Repository navigation
chore(main): release 4.0.0 - #122
Merged
Merged
Conversation
Disable merged release PRs now that the workspace contains only jt, so the branch component matches the Rust release strategy. Reuse the 4.0.0 metadata already generated by release-please without changing versions again.
Contributor
|
🤖 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
PR #120 already merged the automatically generated 4.0.0 versions and changelog. Its grouped branch omitted the jt component, so release-please skipped publication. This recovery PR disables cargo-workspace merging for the remaining jt crate and carries the same generated release metadata on the component branch. No versions are changed again.
Validation: the configuration check and all 247 Rust tests passed locally. The normal Rust and Web CI gates must pass before merging.
4.0.0
4.0.0 (2026-10-20)
⚠ BREAKING CHANGES
Documentation
Code Refactoring
This PR was generated with Release Please. See documentation.