Skip to content

chore(main): release 0.2.6#463

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

chore(main): release 0.2.6#463
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.6 (2026-03-15)

Features

  • add intra-loop stagnation detector (#415) (#458) (8e9f34f)
  • add RFC 9457 structured error responses (Phase 1) (#457) (6612a99), closes #419
  • implement AgentStateRepository for runtime state persistence (#459) (5009da7)
  • site: add SEO essentials, contact form, early-access banner (#467) (11b645e), closes #466

Bug Fixes

  • CLI improvements — config show, completion install, enhanced doctor, Sigstore verification (#465) (9e08cec)
  • site: add reCAPTCHA v3, main landmark, and docs sitemap (#469) (fa6d35c)
  • use force-tag-creation instead of manual tag creation hack (#462) (2338004)

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

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 automates the release of version 0.2.6 for the project. It integrates a significant new feature: the first phase of implementing RFC 9457 structured error responses, enhancing how errors are handled and communicated within the system.

Highlights

  • Version Release: The project has been updated to version 0.2.6, which includes the initial phase of RFC 9457 structured error responses.
Changelog
  • .github/CHANGELOG.md
    • Added a new entry for version 0.2.6, documenting the inclusion of RFC 9457 structured error responses (Phase 1).
Activity
  • An automated release process, managed by Release Please, created this pull request.
  • The project's version has been incremented to 0.2.6.
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: 7abb0409-8208-494f-8b2e-6d1242c359c6

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.

@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 19:02 — 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 automates the release of version 0.2.6. The version bumps in the project files are correct for a release. However, I've identified an issue in the generated CHANGELOG.md where the release date is set in the future. Please see my specific comment for details.

@@ -1,5 +1,12 @@
# Changelog

## [0.2.6](https://github.com/Aureliolo/synthorg/compare/v0.2.5...v0.2.6) (2026-03-15)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The release date (2026-03-15) is set in the future. This appears to be a recurring issue, as the previous release v0.2.5 shares the same date. This likely indicates a configuration error in the release automation tool that should be corrected to reflect the actual release date.

@Aureliolo Aureliolo force-pushed the release-please--branches--main--components--synthorg branch from ff4660f to 4acec4a Compare March 15, 2026 19:08
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 19:09 — with GitHub Actions Inactive
@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.76%. Comparing base (5009da7) to head (2b122cb).
⚠️ Report is 8 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #463   +/-   ##
=======================================
  Coverage   93.76%   93.76%           
=======================================
  Files         476      476           
  Lines       22616    22616           
  Branches     2180     2180           
=======================================
  Hits        21207    21207           
  Misses       1098     1098           
  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 force-pushed the release-please--branches--main--components--synthorg branch from 4acec4a to eb5be5d Compare March 15, 2026 19:24
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 19:25 — with GitHub Actions Inactive
@Aureliolo Aureliolo force-pushed the release-please--branches--main--components--synthorg branch from eb5be5d to 7258062 Compare March 15, 2026 19:53
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 19:54 — with GitHub Actions Inactive
@Aureliolo Aureliolo force-pushed the release-please--branches--main--components--synthorg branch from 7258062 to affe1e0 Compare March 15, 2026 21:29
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 21:30 — with GitHub Actions Inactive
@Aureliolo Aureliolo force-pushed the release-please--branches--main--components--synthorg branch from affe1e0 to f450627 Compare March 15, 2026 21:56
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 21:57 — with GitHub Actions Inactive
@Aureliolo Aureliolo force-pushed the release-please--branches--main--components--synthorg branch from f450627 to 2b122cb Compare March 15, 2026 22:11
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 22:12 — with GitHub Actions Inactive
@Aureliolo Aureliolo merged commit 57cb86d into main Mar 15, 2026
31 checks passed
@Aureliolo Aureliolo deleted the release-please--branches--main--components--synthorg branch March 15, 2026 22:15
@Aureliolo Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 22:15 — with GitHub Actions Inactive
@Aureliolo
Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

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.

feat(site): add SEO essentials, contact form, and early-access disclaimer feat: implement RFC 9457 structured error responses for API

1 participant