Repository navigation
chore(release): fast-forward/fork v1.1.0 → v1.1.1 - #12
Merged
Merged
Conversation
Changelog-Plan: 338631f38391799cb70213dcd51cadedf6bfb0dd5e5a7b22ffb0fa489c5df7d2 Changelog-Base: fdf98ce Changelog-Output: cfbd9cdb675b1ad7241521e1a90d46e86b59bd3d21f4786bb82e6cfd99f374b9 Changelog-Options: 54c0a0516aa6f82372432978b34bd7058a2ec094f9d7c4fbb388fff34bf8cd81
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
Contributor
Author
Changelog✅ Contribution check passed. Head: Base: Contribution: 0 new valid fragment(s). Policy: managed-version. |
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.
Prepare release 1.1.1.
Plan:
338631f38391799cb70213dcd51cadedf6bfb0dd5e5a7b22ffb0fa489c5df7d2Base:
fdf98ce170bf44e46ece3fd45be5344bdfccf8e1Consumed fragments: 2
Updates the changelog and removes the consumed fragments.
Preparing this PR does not publish a tag or release.
After the approved merge, the full lifecycle publishes its tag and GitHub release by default.
An explicit
publish: falsecreates neither; later plans still continue from the consolidated history.Older consolidations without publication are not published retroactively.