Repository navigation
chore(main): release 1.11.0 - #161
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
April 23, 2026 07:40
ef42214 to
834bece
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
April 23, 2026 08:08
834bece to
2b42b38
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
April 24, 2026 22:57
b25d415 to
d601aef
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
4 times, most recently
from
July 30, 2026 13:20
497b119 to
3895970
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
July 30, 2026 13:56
3895970 to
76f7738
Compare
Two accuracy gaps in the generated 1.11.0 notes: 1. #180 was silently omitted. release-please's conventional-commit parser failed on the squash message body: "commit could not be parsed: e7e797f feat(orchestration): ... error: unexpected token '(' at 194:16, valid tokens [)]" Line 194 col 16 is the nested paren in `json.dumps(str(path))`. The commit was skipped entirely, so the MCP server, RunRegistry and ProviderBatchBackend were missing from the release notes. 2. `ondine.enrich()` shipped under a `docs(readme):` commit (#175), so a new public API landed in the Documentation section where nobody would find it. Promoted to Features. Version 1.11.0 is unaffected — the other feat: commits already implied a minor bump.
ptimizeroracle
approved these changes
Jul 30, 2026
ptimizeroracle
left a comment
Owner
There was a problem hiding this comment.
Release 1.11.0 — approved.
CI green across the full matrix (12/12: ubuntu/macOS/windows x py3.10-3.13), all three security scans passing, Build Package and Claim Verification green.
Changelog manually corrected in 2e538ee: release-please's parser dropped #180 entirely (unexpected token '(' at 194:16 — nested parens in the squash body), and ondine.enrich() was filed under Documentation because #175 was typed docs(readme):. Both restored under Features.
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
1.11.0 (2026-07-30)
Features
Bug Fixes
Dependencies
Documentation
This PR was generated with Release Please. See documentation.