Skip to content

chore(main): release 0.2.3#430

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

chore(main): release 0.2.3#430
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.3 (2026-03-15)

Bug Fixes

  • use draft releases to support immutable release policy (#429) (a6c7444)

This PR was generated with Release Please. See documentation.

@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 represents an automated release for version 0.2.3 of the synthorg project. It primarily incorporates a bug fix that ensures draft releases are utilized to maintain an immutable release policy, enhancing the robustness of the release process.

Highlights

  • Version Bump: The project version has been updated from 0.2.2 to 0.2.3 across various configuration and source files.
  • Bug Fix Integration: This release incorporates a bug fix that ensures draft releases are used to support an immutable release policy, addressing issue fix: use draft releases to support immutable release policy #429.
Changelog
  • .github/.release-please-manifest.json
    • Updated the tracked version to 0.2.3.
  • .github/CHANGELOG.md
    • Added release notes for version 0.2.3, including a bug fix for draft releases.
  • pyproject.toml
    • Updated the project version to 0.2.3 in the commitizen configuration.
  • src/synthorg/init.py
    • Updated the __version__ string to 0.2.3.
Activity
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. ↩

@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: 0823b2b5-618c-4742-863d-40ee79d0ba12

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 Please PR that bumps the package version from 0.2.2 to 0.2.3 in all four relevant locations. No logic or behavioural changes are included.

  • .github/.release-please-manifest.json — manifest version updated to "0.2.3"
  • .github/CHANGELOG.md — new 0.2.3 entry prepended referencing the draft-release bug fix from fix: use draft releases to support immutable release policy #429
  • pyproject.toml — [tool.commitizen] version tag bumped to "0.2.3"
  • src/synthorg/__init__.py — __version__ updated to "0.2.3" (the canonical source used by the dynamic pyproject.toml build)

All four version strings are consistent. No issues found.

Confidence Score: 5/5

  • This PR is safe to merge — it is a pure automated version bump with no code changes.
  • All four changed files receive only mechanical version string updates from 0.2.2 to 0.2.3, all are consistent with each other, and no logic or configuration beyond version identifiers was modified.
  • No files require special attention.

Important Files Changed

Filename Overview
.github/.release-please-manifest.json Version bumped from "0.2.2" to "0.2.3" — consistent with all other version files.
.github/CHANGELOG.md New 0.2.3 changelog entry prepended with the correct bug-fix reference and commit link.
pyproject.toml Commitizen version tag bumped from "0.2.2" to "0.2.3"; project version is dynamic so no second update needed.
src/synthorg/init.py __version__ bumped from "0.2.2" to "0.2.3", serving as the canonical version source for the dynamic pyproject.toml build.

Last reviewed commit: 9e794c8

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 is an automated release pull request that bumps the version to 0.2.3. The version updates are consistent across all files. I've left one minor suggestion regarding the formatting of the CHANGELOG.md file.

.github/CHANGELOG.md

## [0.2.3](https://github.com/Aureliolo/synthorg/compare/v0.2.2...v0.2.3) (2026-03-15)


Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Mar 15, 2026

Choose a reason for hiding this comment

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

medium

To improve readability and maintain a consistent style, it's best to remove this extra blank line. Typically, only a single blank line is used to separate block-level elements in Markdown.

@Aureliolo Aureliolo merged commit 440c540 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:54
@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:54 — with GitHub Actions Inactive
@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 (e69263a) to head (9e794c8).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #430   +/-   ##
=======================================
  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

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.

1 participant

@Aureliolo