Skip to content

chore: reset failed v0.3.7 release#591

Merged
Aureliolo merged 2 commits intomainfrom
chore/reset-failed-release
Mar 19, 2026
Merged

chore: reset failed v0.3.7 release#591
Aureliolo merged 2 commits intomainfrom
chore/reset-failed-release

Conversation

@Aureliolo
Copy link
Copy Markdown
Owner

@Aureliolo Aureliolo commented Mar 19, 2026

Summary

Reverts the Release Please commit for v0.3.7 (bf58779) because the CLI GoReleaser step failed during the release workflow (LICENSE path resolution error). The draft release and tag have been deleted.

What this reverts:

  • .github/.release-please-manifest.json: 0.3.7 -> 0.3.6
  • .github/CHANGELOG.md: removes 0.3.7 entry
  • pyproject.toml: 0.3.7 -> 0.3.6
  • src/synthorg/__init__.py: 0.3.7 -> 0.3.6

What was already cleaned up:

  • Deleted draft GitHub Release for v0.3.7
  • Deleted remote tag v0.3.7

Next steps:

  1. Merge this PR (resets version to 0.3.6)
  2. Merge fix(cli): auto-delete binary on Windows, prune images, fix GoReleaser #590 (fixes GoReleaser LICENSE path + uninstall improvements)
  3. Release Please will auto-create a new release PR for 0.3.7 that includes all fixes
  4. Merging that release PR will re-trigger Docker + CLI workflows with the GoReleaser fix in place

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Version updated from 0.3.7 to 0.3.6 across configuration and version metadata files.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 19, 2026

Dependency Review

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

Scanned Files

None

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 19, 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: dc99f4f8-bcd4-4dc6-a3f2-969ab614a5fb

📥 Commits

Reviewing files that changed from the base of the PR and between bf58779 and e634f51.

📒 Files selected for processing (4)
  • .github/.release-please-manifest.json
  • .github/CHANGELOG.md
  • pyproject.toml
  • src/synthorg/__init__.py
💤 Files with no reviewable changes (1)
  • .github/CHANGELOG.md
📜 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). (6)
  • GitHub Check: Deploy Preview
  • GitHub Check: Test (Python 3.14)
  • GitHub Check: Build Backend
  • GitHub Check: Build Sandbox
  • GitHub Check: Build Web
  • GitHub Check: Analyze (python)
🧰 Additional context used
📓 Path-based instructions (3)
pyproject.toml

📄 CodeRabbit inference engine (CLAUDE.md)

All Python dependency versions must use == for pinned versions in [project.dependencies] and [tool.uv.sources]

Files:

  • pyproject.toml
**/*.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) following PEP 758 — ruff enforces this on Python 3.14
All public functions and classes must have type hints — mypy strict mode is enforced
Docstrings must follow Google style format and are required on all public classes and functions — enforced by ruff D rules
Line length must be 88 characters — enforced by ruff
Functions must be fewer than 50 lines and files must be fewer than 800 lines
Handle errors explicitly — never silently swallow exceptions
Validate at system boundaries (user input, external APIs, config files)
Use Pydantic v2 with BaseModel, model_validator, computed_field, and ConfigDict
Use @computed_field for derived values instead of storing and validating redundant fields (e.g., TokenUsage.total_tokens)
Use NotBlankStr (from core.types) for all identifier and name fields — including optional (NotBlankStr | None) and tuple (tuple[NotBlankStr, ...]) variants — instead of manual whitespace validators
Prefer asyncio.TaskGroup for fan-out/fan-in parallel operations in new code (e.g., multiple tool invocations, parallel agent calls) — use structured concurrency over bare create_task
Create new objects rather than mutating existing ones — use copy.deepcopy() at construction and MappingProxyType wrapping for read-only enforcement on non-Pydantic internal collections
Use frozen Pydantic models for config and identity; use separate mutable-via-copy models (with model_copy(update=...)) for runtime state that evolves — never mix static config fields with mutable runtime fields in one model
All provider calls must go through BaseCompletionProvider which applies retry and rate limiting automatically — never implement retry logic in driver subclasses or calling code
RetryConfig and RateLimiterConfig are set per-provider in ProviderConfig — retryable errors (RateLimitError, `ProviderTime...

Files:

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

📄 CodeRabbit inference engine (CLAUDE.md)

src/synthorg/**/*.py: Every module with business logic must import logger via from synthorg.observability import get_logger and create logger = get_logger(__name__)
Never use import logging, logging.getLogger(), or print() in application code — use the logger from synthorg.observability
Logger variable must always be named logger (not _logger or log)
Event names must always use constants from domain-specific modules under synthorg.observability.events (e.g., API_REQUEST_STARTED from events.api, TOOL_INVOKE_START from events.tool)
Use structured logging with keyword arguments: logger.info(EVENT, key=value) — never use format strings like logger.info('msg %s', val)
All error paths must log at WARNING or ERROR level with context before raising an exception
All state transitions must log at INFO level
DEBUG logging should be used for object creation, internal flow, and entry/exit of key functions
Pure data models, enums, and re-exports do NOT need logging

Files:

  • src/synthorg/__init__.py
🔇 Additional comments (3)
.github/.release-please-manifest.json (1)

2-2: LGTM! Version revert is correct.

The version mapping has been correctly updated from 0.3.7 to 0.3.6, aligning with the PR's objective to reset the failed release. This change is consistent with the corresponding updates in pyproject.toml and src/synthorg/__init__.py.

src/synthorg/__init__.py (1)

3-3: LGTM! Version constant correctly reverted.

The __version__ constant has been properly updated from "0.3.7" to "0.3.6", maintaining consistency with the version changes in .github/.release-please-manifest.json and pyproject.toml. The x-release-please-version marker comment is correctly preserved.

pyproject.toml (1)

220-220: LGTM! Commitizen version correctly reverted.

The commitizen version has been properly updated from "0.3.7" to "0.3.6", maintaining consistency with the version changes in .github/.release-please-manifest.json and src/synthorg/__init__.py. The x-release-please-version marker comment is correctly preserved, enabling automated version management.


Walkthrough

This pull request reverts the package version from 0.3.7 to 0.3.6 across multiple configuration and source files. The changes include updating the release manifest version mapping, removing the 0.3.7 changelog entry, updating the commitizen version configuration, and decrementing the __version__ constant in the package initialization file.

Suggested labels

autorelease: tagged

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: reverting a failed v0.3.7 release by resetting version numbers back to 0.3.6 across all relevant files.
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
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch chore/reset-failed-release
📝 Coding Plan
  • Generate coding plan for human review comments

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

@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 addresses a failed v0.3.7 release by reverting the associated changes. The release process encountered an error with GoReleaser's LICENSE path resolution. This PR restores the project's versioning to 0.3.6 across relevant configuration and source files, and removes the incomplete 0.3.7 changelog entry, preparing the repository for a corrected re-release.

Highlights

  • Reverted Failed Release: The v0.3.7 release was reverted due to a GoReleaser step failure during the CLI release workflow, specifically a LICENSE path resolution error.
  • Version Rollback: Key versioning files, including .github/.release-please-manifest.json, pyproject.toml, and src/synthorg/__init__.py, have been rolled back from version 0.3.7 to 0.3.6.
  • Changelog Update: The entire changelog entry for version 0.3.7 has been removed from .github/CHANGELOG.md.
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.

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 temporarily deployed to cloudflare-preview March 19, 2026 13:51 — with GitHub Actions Inactive
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 reverts the project version from 0.3.7 to 0.3.6 to reset a failed release. The changes correctly update the version in pyproject.toml, src/synthorg/__init__.py, and .github/.release-please-manifest.json, and remove the v0.3.7 entry from the changelog. The changes are consistent and appropriate for the stated goal. I have no further feedback as the modifications are correct.

coderabbitai[bot]
coderabbitai bot previously approved these changes Mar 19, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.46%. Comparing base (bf58779) to head (503d3a6).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #591   +/-   ##
=======================================
  Coverage   92.46%   92.46%           
=======================================
  Files         551      551           
  Lines       27681    27681           
  Branches     2678     2678           
=======================================
  Hits        25595    25595           
  Misses       1634     1634           
  Partials      452      452           

☔ 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.

test_stops_at_max_depth used capsys to capture stdout, but
walk_string_values logs via structlog (logger.warning), not print().
Replace with @patch on the logger and assert warning was called with
the depth kwarg -- future-proof regardless of structlog sink config.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 19, 2026 14:12 — with GitHub Actions Inactive
@Aureliolo Aureliolo merged commit b69000d into main Mar 19, 2026
32 checks passed
@Aureliolo Aureliolo deleted the chore/reset-failed-release branch March 19, 2026 14:16
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 19, 2026 14:16 — with GitHub Actions Inactive
Aureliolo added a commit that referenced this pull request Mar 19, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.3.7](v0.3.6...v0.3.7)
(2026-03-19)


### Features

* **engine:** implement Hybrid Plan + ReAct execution loop
([#582](#582))
([008147c](008147c))
* implement first-run setup wizard
([#584](#584))
([dfed931](dfed931))


### Bug Fixes

* **api:** address ZAP DAST scan findings
([#579](#579))
([ce9a3e0](ce9a3e0))
* **cli:** auto-delete binary on Windows, prune images, fix GoReleaser
([#590](#590))
([eb7c691](eb7c691))
* **cli:** regenerate compose and re-exec binary on update
([#576](#576))
([3f226eb](3f226eb))


### CI/CD

* add SBOM generation to Docker and CLI releases
([#580](#580))
([db459cf](db459cf))


### Maintenance

* **main:** release 0.3.7
([#583](#583))
([bf58779](bf58779))
* reset failed v0.3.7 release
([#591](#591))
([b69000d](b69000d))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **New Features**
  * Added engine Hybrid Plan + ReAct execution loop
  * Added first-run setup wizard

* **Bug Fixes**
  * Addressed ZAP DAST scan issues
  * Fixed CLI Windows/image/update issues

* **Maintenance**
  * Added SBOM generation for Docker/CLI releases
  * General maintenance updates

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
This was referenced Mar 19, 2026
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