Repository navigation
chore(release): fast-forward/config v1.7.3 → v1.7.4 - #48
Merged
Merged
Conversation
Changelog-Plan: 69dced808215b0a9e8d3aea800c44269321264a780a027634441ef1a904e89f4 Changelog-Base: 6d22444 Changelog-Output: 646fe6e0fb27c13d607a1d6e689dc8121e27d8721ee917e1f8e42e580e346fe3 Changelog-Options: 0717ef19b3c8b48c9aa5819741a2a3477ea0ce65701e0ce03063e95bfa9c66d2
|
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.7.4.
Plan:
69dced808215b0a9e8d3aea800c44269321264a780a027634441ef1a904e89f4Base:
6d224443c3c99b8f8a936ced80ee6cdd6ed808b5Consumed fragments: 4
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.