Skip to content

chore: reset version to 0.2.3 for re-release#444

Merged
Aureliolo merged 1 commit intomainfrom
fix/reset-release-manifest
Mar 15, 2026
Merged

chore: reset version to 0.2.3 for re-release#444
Aureliolo merged 1 commit intomainfrom
fix/reset-release-manifest

Conversation

@Aureliolo
Copy link
Copy Markdown
Owner

Summary

  • Reset .github/.release-please-manifest.json, pyproject.toml, and src/synthorg/__init__.py from 0.2.4 back to 0.2.3
  • The v0.2.4 draft release and tag were deleted because the CLI Release job failed (cosign --bundle format issue, fixed in fix: use cosign --bundle flag for checksums signing #443)
  • After merging this, Release Please will see all commits since v0.2.3 and create a fresh v0.2.4 release PR that includes the cosign fix

Context

  1. v0.2.4 tag was created by Release Please
  2. CLI Release job failed at cosign signing (deprecated --output-signature/--output-certificate flags)
  3. Draft release had 0 assets (no CLI binaries uploaded)
  4. Fix merged in fix: use cosign --bundle flag for checksums signing #443 but the tag was already created from pre-fix code
  5. Deleted the v0.2.4 draft release and tag
  6. This PR resets versions so Release Please can re-create v0.2.4 cleanly

Test plan

The v0.2.4 tag and draft release were deleted because the CLI Release
job failed (cosign --bundle format). Reset manifest, pyproject.toml,
and __init__.py to 0.2.3 so Release Please re-creates v0.2.4 with the
cosign fix included.
@github-actions
Copy link
Copy Markdown
Contributor

Dependency Review

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

Scanned Files

None

@gemini-code-assist
Copy link
Copy Markdown
Contributor

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 prepares the repository for a successful v0.2.4 release by reverting all version indicators back to 0.2.3. This action is a direct response to a previously failed v0.2.4 release, which was halted due to a cosign signing error. With the underlying issue now resolved in a separate fix, this PR ensures that the automated release system can correctly identify all pending changes and generate a clean, fully functional v0.2.4 release.

Highlights

  • Version Reset: The project's version was reverted from "0.2.4" to "0.2.3" across .github/.release-please-manifest.json, pyproject.toml, and src/synthorg/__init__.py.
  • Release Failure Remediation: This change addresses a failed v0.2.4 release attempt, which encountered a cosign --bundle format issue. The previous v0.2.4 draft release and tag were deleted.
  • Enabling Clean Re-release: By resetting the version, Release Please is expected to generate a new v0.2.4 release PR that correctly incorporates the cosign fix from fix: use cosign --bundle flag for checksums signing #443.
Changelog
  • .github/.release-please-manifest.json
    • Reverted the project version from "0.2.4" to "0.2.3".
  • pyproject.toml
    • Reverted the commitizen tool's version from "0.2.4" to "0.2.3".
  • src/synthorg/init.py
    • Reverted the __version__ string from "0.2.4" to "0.2.3".
Activity
  • The v0.2.4 tag was initially created by Release Please.
  • The CLI Release job subsequently failed during cosign signing due to deprecated flags.
  • The draft release for v0.2.4 had no assets uploaded.
  • A fix for the cosign issue was merged in fix: use cosign --bundle flag for checksums signing #443, but the v0.2.4 tag had already been created from pre-fix code.
  • The v0.2.4 draft release and tag were deleted to allow for a clean re-release.
  • This pull request was created to reset the version numbers, enabling Release Please to correctly re-create v0.2.4.
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.

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 resets the project version from 0.2.4 back to 0.2.3 in .github/.release-please-manifest.json, pyproject.toml, and src/synthorg/__init__.py. This is a procedural change to allow release-please to correctly generate a new v0.2.4 release after a previous attempt failed. The changes are consistent and correct for the stated purpose, and I find no issues.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 15, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a09b1059-a9b0-45cf-b284-bef4293bf713

📥 Commits

Reviewing files that changed from the base of the PR and between 19735b9 and 9124d2b.

📒 Files selected for processing (3)
  • .github/.release-please-manifest.json
  • pyproject.toml
  • src/synthorg/__init__.py
📜 Recent review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Test (Python 3.14)
  • GitHub Check: Build Backend
🧰 Additional context used
📓 Path-based instructions (3)
**/*.py

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.py: No from __future__ import annotations — Python 3.14 has PEP 649 native lazy annotations
Use except A, B: syntax (no parentheses) instead of except (A, B): — PEP 758 syntax enforced by ruff on Python 3.14
All public functions must have type hints; mypy strict mode is enforced
Use Google-style docstrings on all public classes and functions (enforced by ruff D rules)
Use NotBlankStr from core.types for all identifier/name fields (including optional and tuple variants) instead of manual whitespace validators
Use @computed_field in Pydantic models for derived values instead of storing and validating redundant fields
Prefer asyncio.TaskGroup for fan-out/fan-in parallel operations (e.g., multiple tool invocations, parallel agent calls) instead of bare create_task
Line length: 88 characters (enforced by ruff)
Functions must be < 50 lines; files must be < 800 lines
Handle errors explicitly; never silently swallow exceptions
Validate input at system boundaries (user input, external APIs, config files)
Create new objects instead of mutating existing ones (immutability principle)

Files:

  • src/synthorg/__init__.py
src/synthorg/**/*.py

📄 CodeRabbit inference engine (CLAUDE.md)

src/synthorg/**/*.py: Every module with business logic must import from synthorg.observability import get_logger and define logger = get_logger(__name__)
Never use import logging, logging.getLogger(), or print() in application code — use the synthorg logger instead
Always use event name constants from domain-specific modules under synthorg.observability.events (e.g., PROVIDER_CALL_START from events.provider); import directly: from synthorg.observability.events.<domain> import EVENT_CONSTANT
Always log with structured kwargs: logger.info(EVENT, key=value) — never use old-style formatting logger.info("msg %s", val)
All error paths must log at WARNING or ERROR with context before raising
All state transitions must log at INFO level
Use DEBUG level for object creation, internal flow, and entry/exit of key functions
Pure data models, enums, and re-exports do NOT need logging
Never implement retry logic in driver subclasses or calling code — all provider calls go through BaseCompletionProvider which applies retry + rate limiting automatically
Set RetryConfig and RateLimiterConfig per-provider in ProviderConfig; retryable errors are RateLimitError, ProviderTimeoutError, ProviderConnectionError, ProviderInternalError
Use frozen Pydantic models for config/identity; separate mutable-via-copy models (using model_copy(update=...)) for runtime state
For dict/list fields in frozen Pydantic models, use copy.deepcopy() at system boundaries (tool execution, LLM provider serialization, inter-agent delegation, persistence serialization)
Use Pydantic v2 conventions: BaseModel, model_validator, computed_field, ConfigDict

Files:

  • src/synthorg/__init__.py
pyproject.toml

📄 CodeRabbit inference engine (CLAUDE.md)

All Python dependency versions must use == pinning (not >=, ~=, etc.)

Files:

  • pyproject.toml
🧠 Learnings (2)
📚 Learning: 2026-03-15T12:05:56.884Z
Learnt from: CR
Repo: Aureliolo/synthorg PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-15T12:05:56.884Z
Learning: Applies to **/.git/** : Use commit message format: `<type>: <description>` (types: feat, fix, refactor, docs, test, chore, perf, ci) enforced by commitizen

Applied to files:

  • pyproject.toml
📚 Learning: 2026-03-15T11:48:14.867Z
Learnt from: CR
Repo: Aureliolo/synthorg PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-15T11:48:14.867Z
Learning: Commits: <type>: <description> — types: feat, fix, refactor, docs, test, chore, perf, ci. Enforced by commitizen (commit-msg hook). Signed commits: required on main via branch protection — all commits must be GPG/SSH signed.

Applied to files:

  • pyproject.toml
🔇 Additional comments (3)
.github/.release-please-manifest.json (1)

2-2: Release manifest rollback is correct.

Setting the manifest root to 0.2.3 correctly resets Release Please state for re-cutting v0.2.4.

pyproject.toml (1)

218-218: Commitizen version reset is aligned with the release rollback.

Updating this marker to 0.2.3 keeps tooling metadata consistent with the manifest and package version reset.

src/synthorg/__init__.py (1)

3-3: __version__ rollback is correct.

This keeps the exported package version synchronized with the release metadata reset.


📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated version number to 0.2.3 across release configuration and package metadata.

Walkthrough

Version downgrade from 0.2.4 to 0.2.3 across release manifest, project configuration, and module version export. No functional or control-flow changes.

Changes

Cohort / File(s) Summary
Version Downgrade
.github/.release-please-manifest.json, pyproject.toml, src/synthorg/__init__.py
Reverted version from 0.2.4 to 0.2.3 in release manifest, commitizen configuration, and module __version__ export.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

autorelease: tagged

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and accurately describes the main change: resetting the version to 0.2.3 for a re-release after a failed v0.2.4 release.
Description check ✅ Passed The description is comprehensive and directly related to the changeset, explaining the rationale for reverting versions, the context of the failed v0.2.4 release, and the expected outcome.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/reset-release-manifest
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch fix/reset-release-manifest
📝 Coding Plan
  • Generate coding plan for human review comments

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

@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 12:51 — with GitHub Actions Inactive
@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Mar 15, 2026

Greptile Summary

This PR resets the package version from 0.2.4 back to 0.2.3 across all three Release Please-managed version locations after a failed v0.2.4 release cycle (CLI cosign signing failure left the draft release empty). The rollback is clean and correct, allowing Release Please to regenerate a fresh v0.2.4 release PR that incorporates the cosign fix from #443.

  • .github/.release-please-manifest.json: "0.2.4""0.2.3" (Release Please manifest)
  • pyproject.toml ([tool.commitizen]): version = "0.2.4"version = "0.2.3" (commitizen + Release Please marker)
  • src/synthorg/__init__.py: __version__ = "0.2.4"__version__ = "0.2.3" (authoritative source read by hatchling for package builds)

All three version strings are consistent with each other and with the v0.2.3 baseline. No logic, tests, or configuration beyond version strings are touched. No issues found.

Confidence Score: 5/5

  • This PR is safe to merge — it is a purely mechanical version reset with no behavioral changes.
  • All three version-tracking files are updated consistently to 0.2.3. The hatchling build backend reads __version__ from src/synthorg/__init__.py, commitizen reads from pyproject.toml, and Release Please reads from the manifest — all are now in sync. No code logic, tests, or CI workflows are modified.
  • No files require special attention.

Important Files Changed

Filename Overview
.github/.release-please-manifest.json Version reset from 0.2.4 to 0.2.3 — consistent with the PR intent and aligns with the other two version files.
pyproject.toml Version reset in [tool.commitizen] from 0.2.4 to 0.2.3 via the x-release-please-version marker — correct and consistent.
src/synthorg/init.py version reset from 0.2.4 to 0.2.3 — this is the authoritative source read by hatchling for the package version, so correctness here is critical; the value is right.

Last reviewed commit: 9124d2b

@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 (63b03c4) to head (9124d2b).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #444   +/-   ##
=======================================
  Coverage   93.67%   93.67%           
=======================================
  Files         469      469           
  Lines       22213    22213           
  Branches     2144     2144           
=======================================
  Hits        20808    20808           
  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.

@Aureliolo Aureliolo merged commit 8579993 into main Mar 15, 2026
33 checks passed
@Aureliolo Aureliolo deleted the fix/reset-release-manifest branch March 15, 2026 13:05
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 13:05 — with GitHub Actions Inactive
Aureliolo added a commit that referenced this pull request Mar 15, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.2.4](v0.2.3...v0.2.4)
(2026-03-15)


### Bug Fixes

* attach cosign signatures and provenance bundle to release assets
([#438](#438))
([f191a4d](f191a4d))
* create git tag explicitly for draft releases
([#432](#432))
([1f5120e](1f5120e))
* docker healthcheck, CI optimization, and container hardening
([#436](#436))
([4d32bca](4d32bca))
* ensure security headers on all HTTP responses
([#437](#437))
([837f2fc](837f2fc))
* make install scripts usable immediately without terminal restart
([#433](#433))
([b45533c](b45533c))
* migrate pids_limit to deploy.resources.limits.pids
([#439](#439))
([66b94fd](66b94fd))
* use cosign --bundle flag for checksums signing
([#443](#443))
([19735b9](19735b9))


### Refactoring

* redesign release notes layout
([#434](#434))
([239aaf7](239aaf7))


### Maintenance

* **main:** release 0.2.4
([#431](#431))
([63b03c4](63b03c4))
* remove stale v0.2.4 changelog section from failed release
([#446](#446))
([769de10](769de10))
* reset version to 0.2.3 for re-release
([#444](#444))
([8579993](8579993))
* **site:** replace hero CTA with license link and scroll arrow
([#440](#440))
([56af41c](56af41c))
* **web:** adopt @vue/tsconfig preset
([#435](#435))
([7d4b214](7d4b214))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant