Skip to content

chore(main): release 0.2.1#426

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

chore(main): release 0.2.1#426
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.1 (2026-03-15)

Bug Fixes

  • upgrade goreleaser to v2.14.3 (v2.11.3 never existed) (#425) (df6650d)

This PR was generated with Release Please. See documentation.

Copilot AI review requested due to automatic review settings March 15, 2026 00:50
@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: 28ad1252-151f-4c50-a4ae-876156e32551

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.

@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.1 of the project. Its primary purpose is to update all relevant versioning metadata across the repository and formally incorporate a specific bug fix that addresses an incorrect goreleaser version. This ensures that the project's official release artifacts and documentation reflect the latest stable state.

Highlights

  • New Release Version: The project has been released as version 0.2.1.
  • Bug Fix: A bug related to the goreleaser version has been fixed, upgrading it to v2.14.3.
Changelog
Activity
  • This pull request was automatically generated by a release bot.
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. ↩

@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 project version from 0.2.0 to 0.2.1, incorporating the goreleaser version fix from PR #425. All four version-bearing locations are updated consistently and correctly.

  • .github/.release-please-manifest.json — manifest version updated to 0.2.1
  • .github/CHANGELOG.md — new 0.2.1 entry prepended with the correct bug-fix reference
  • pyproject.toml — [tool.commitizen] version updated to 0.2.1; the [project] version correctly stays dynamic (sourced from __init__.py via hatchling — no change needed there)
  • src/synthorg/__init__.py — __version__ updated to 0.2.1, which is the single source of truth consumed by the build system

Confidence Score: 5/5

  • This PR is safe to merge — it is a purely mechanical, auto-generated version bump with no logic changes.
  • All four files have consistent, correct version strings (0.2.1). The dynamic version setup in pyproject.toml is untouched and correctly defers to __init__.py. No logic, dependencies, or configuration were modified beyond the version strings and changelog.
  • No files require special attention.

Important Files Changed

Filename Overview
.github/.release-please-manifest.json Version bumped from "0.2.0" to "0.2.1" — correct and consistent with the rest of the release.
.github/CHANGELOG.md New 0.2.1 changelog entry prepended correctly, referencing PR #425 and the goreleaser version fix.
pyproject.toml Commitizen version bumped from "0.2.0" to "0.2.1"; project version remains dynamic (sourced from init.py via hatchling), so no second update is needed.
src/synthorg/init.py version bumped from "0.2.0" to "0.2.1"; this is the single source of truth for the package version consumed by hatchling.

Last reviewed commit: af13ddb

@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 00:51 — with GitHub Actions Inactive
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, generated by Release Please, bumps the version to 0.2.1 across several files to release a bug fix. The changes are consistent, but I've noted an issue with the release date in the changelog, which is set to a future date. This should be corrected to avoid confusion.

.github/CHANGELOG.md
@@ -1,5 +1,12 @@
# Changelog

## [0.2.1](https://github.com/Aureliolo/synthorg/compare/v0.2.0...v0.2.1) (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

The release date is set to a future date (2026-03-15). This is misleading for users reading the changelog and is likely a configuration issue with the release automation tool. I've suggested removing the date for now, but the ideal fix would be to configure the automation to use the correct release date.

Suggested change
## [0.2.1](https://github.com/Aureliolo/synthorg/compare/v0.2.0...v0.2.1) (2026-03-15)
## [0.2.1](https://github.com/Aureliolo/synthorg/compare/v0.2.0...v0.2.1)

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 version bump to publish SynthOrg v0.2.1, aligning repository metadata (runtime, tooling, and release manifest) and recording the release notes.

Changes:

  • Bump Python runtime version (__version__) to 0.2.1.
  • Bump Commitizen version to 0.2.1 for consistent tagging.
  • Update Release Please manifest and changelog for the 0.2.1 release.

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 runtime __version__ to 0.2.1.
pyproject.toml Updates Commitizen version marker to 0.2.1.
.github/CHANGELOG.md Adds 0.2.1 changelog entry (bugfix note re: GoReleaser version).
.github/.release-please-manifest.json Updates release-please manifest version to 0.2.1.

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

@Aureliolo Aureliolo merged commit e4dfbea into main Mar 15, 2026
28 checks passed
@Aureliolo Aureliolo deleted the release-please--branches--main--components--synthorg branch March 15, 2026 00:53
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 00:53 — with GitHub Actions Inactive
@Aureliolo
Copy link
Copy Markdown
Owner Author

Aureliolo commented Mar 15, 2026

🤖 Created releases:

🌻

@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 (df27c6e) to head (af13ddb).
⚠️ Report is 9 commits behind head on main.
✅ All tests successful. No failed tests found.

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