Repository navigation
chore(release): publish packages - #41
Merged
Merged
Conversation
- nonstop_cli@0.0.8
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.
Release commit produced by
melos version.nonstop_cli0.0.7+4 → 0.0.8.Touches only the three files melos owns:
packages/nonstop_cli/pubspec.yaml— version bumppackages/nonstop_cli/lib/version.dart— kept in sync by theupdate_nonstop_cli_versionpreCommit hookpackages/nonstop_cli/CHANGELOG.md— generated from the conventional commits in feat(nonstop_cli): generate a production-shaped app skeleton #40The bundles were already regenerated and committed in #40, so
update_nonstop_cli_bundleshad nothing to add here.Please merge with a merge commit, not squash
The tag
nonstop_cli-v0.0.8is already on the remote —git push --follow-tagspushed it before the branch push was rejected by themainprotection rule. It points at0795504, the commit in this PR.A merge commit keeps
0795504reachable frommain, so the tag stays valid. Squashing would rewrite it and leave the published tag pointing at a commit that is not onmain.After merge
🤖 Generated with Claude Code