Skip to content

chore(main): release 0.2.2#428

Merged
Aureliolo merged 1 commit intomainfrom
release-please--branches--main--components--synthorg
Mar 15, 2026
Merged

chore(main): release 0.2.2#428
Aureliolo merged 1 commit intomainfrom
release-please--branches--main--components--synthorg

Conversation

@Aureliolo
Copy link
Copy Markdown
Owner

@Aureliolo Aureliolo commented Mar 15, 2026

🤖 I have created a release beep boop

0.2.2 (2026-03-15)

Bug Fixes

  • restore golangci-lint to v2.11.3 (broken by replace_all in #425) (#427) (8ba9375)

This PR was generated with Release Please. See documentation.

Copilot AI review requested due to automatic review settings March 15, 2026 01:00
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 15, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@gemini-code-assist
Copy link
Copy Markdown
Contributor

gemini-code-assist bot commented Mar 15, 2026

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated release for version 0.2.2 of the project. It includes an important bug fix that restores the golangci-lint tool to a working version, resolving an issue introduced in a previous change.

Highlights

  • Version Bump: The project version has been updated from 0.2.1 to 0.2.2 across relevant configuration and source files.
  • Bug Fix: A bug related to golangci-lint was fixed, specifically restoring it to version v2.11.3 after it was broken by a replace_all operation.
Changelog
  • .github/CHANGELOG.md
    • Added the changelog entry for version 0.2.2, detailing a bug fix to restore golangci-lint to v2.11.3.
Activity
  • This pull request was automatically generated by Release Please to publish version 0.2.2.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@Aureliolo Aureliolo merged commit e69263a into main Mar 15, 2026
28 of 29 checks passed
@Aureliolo Aureliolo deleted the release-please--branches--main--components--synthorg branch March 15, 2026 01:00
@Aureliolo
Copy link
Copy Markdown
Owner Author

Aureliolo commented Mar 15, 2026

🤖 Created releases:

🌻

@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 01:00 — with GitHub Actions Inactive
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 15, 2026

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (2)
  • chore(main): release ai-company
  • chore(main): release

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4a66caf8-67c3-4d74-811f-b2f50a7ae066

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-please--branches--main--components--synthorg
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch release-please--branches--main--components--synthorg
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Mar 15, 2026

Greptile Summary

This is an automated release PR generated by Release Please, bumping the package version from 0.2.1 to 0.2.2 to capture the golangci-lint version restore fix from PR #427.

  • src/synthorg/__init__.py: __version__ updated to "0.2.2" — this is the canonical version source read by hatchling at build time
  • pyproject.toml: [tool.commitizen] version field updated to "0.2.2" — consistent with __init__.py
  • .github/.release-please-manifest.json: manifest version updated to "0.2.2" for Release Please state tracking
  • .github/CHANGELOG.md: new 0.2.2 entry prepended, correctly referencing the upstream fix commit

All four version locations are in sync and the changes are exactly what Release Please is expected to produce. No logic, syntax, or style issues found.

Confidence Score: 5/5

  • This PR is safe to merge — it is a fully automated, mechanical version bump with no logic changes.
  • All four changed files contain only version string updates from 0.2.1 to 0.2.2, generated deterministically by Release Please. Version strings are consistent across every location (__init__.py, pyproject.toml, the manifest, and the changelog). There are no code changes, no dependency modifications, and no risk of regressions.
  • No files require special attention.

Important Files Changed

Filename Overview
.github/.release-please-manifest.json Version manifest bumped from 0.2.1 to 0.2.2 by Release Please automation — no issues.
.github/CHANGELOG.md New 0.2.2 changelog entry prepended describing the golangci-lint version restore fix — no issues.
pyproject.toml Commitizen version field bumped from 0.2.1 to 0.2.2; consistent with other version files — no issues.
src/synthorg/init.py Package version bumped from 0.2.1 to 0.2.2; this is the canonical version source read by hatchling — no issues.

Last reviewed commit: ff8fc79

Copilot AI reviewed Mar 15, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Release Please–generated release PR to cut SynthOrg v0.2.2, aligning repository version markers and changelog for the new patch release.

Changes:

  • Bump package version to 0.2.2 in the Python package __version__.
  • Update Commitizen version and Release Please manifest to 0.2.2.
  • Add the 0.2.2 entry to .github/CHANGELOG.md.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
src/synthorg/__init__.py Updates authoritative package __version__ to 0.2.2.
pyproject.toml Updates Commitizen’s tracked version to 0.2.2.
.github/CHANGELOG.md Adds the generated changelog entry for 0.2.2.
.github/.release-please-manifest.json Updates Release Please manifest version to 0.2.2.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

gemini-code-assist[bot]
gemini-code-assist bot reviewed Mar 15, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request contains automated changes for the v0.2.2 release. The version has been updated across pyproject.toml, src/synthorg/__init__.py, and the .release-please-manifest.json. The CHANGELOG.md has also been updated to reflect this new release. The changes are consistent with an automated release workflow, and I found no issues during my review.

@Aureliolo Aureliolo mentioned this pull request Mar 15, 2026
Merged
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.67%. Comparing base (e4dfbea) to head (ff8fc79).
⚠️ Report is 4 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #428   +/-   ##
=======================================
  Coverage   93.67%   93.67%           
=======================================
  Files         469      469           
  Lines       22214    22214           
  Branches     2142     2142           
=======================================
  Hits        20809    20809           
  Misses       1094     1094           
  Partials      311      311

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

This was referenced Mar 15, 2026
Closed
Merged
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Aureliolo