chore(main): release 0.4.0 - #124
Merged
Merged
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a6d020a573
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Contributor
Merging this PR will not alter performance
Comparing 
Footnotes
|
samzong
added a commit
that referenced
this pull request
Aug 11, 2026
…mps (#125) The first release PR proposed 1.0.0 and rewrote both extension crates to that version. Two separate defects, both visible in #124. release-please bumps the major on a breaking change unless told the project is pre-1.0, so #118's feat! took 0.3.0 to 1.0.0. The next version has to be 0.4.0: recall-reflect 0.2.0 already declares min_recall 0.4.0. The rust release type rewrites every member of a Cargo workspace to the released version, so it set recall-probe and recall-reflect to 1.0.0. Those crates version independently — a version bump in their manifest is what their release workflow reads as release intent, so merging that would have published them from the core's version line. The simple release type with an extra-files updater targeting $.package.version touches the root manifest only. Cargo.lock is no longer updated by the release PR as a result; it carries the old version for the root package until the next build regenerates it. Nothing in CI builds with --locked. Signed-off-by: samzong <samzong.lu@gmail.com>
samzong
force-pushed
the
release-please--branches--main--components--recall
branch
from
August 11, 2026 15:40
a6d020a to
3ac61d2
Compare
Owner
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
1 participant
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
0.4.0 (2026-08-11)
⚠ BREAKING CHANGES
Features
Fixes
Performance
Refactors
Documentation
This PR was generated with Release Please. See documentation.