Repository navigation
chore: release the first version as 1.0.0 - #213
Merged
Merged
Conversation
release-please planned the first release as 1.1.0 because the manifest already names 1.0.0 and no release exists, so the config sets release-as 1.0.0 on the root package. docs/release.md now names the Actions setting release-please needs to open its pull request, sends the first release through that pull request instead of a hand-pushed tag, and says to remove release-as once v1.0.0 is tagged.
3 tasks
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.
Sets
release-as: 1.0.0on the root package, so the first release pull request releases 1.0.0 instead of 1.1.0.A release-please 17.11.2 dry run against this branch plans
chore: release 1.0.0and bumpspubspec.yamlfrom1.0.0+1to1.0.0+2.docs/release.mdnow names the Workflow permissions setting release-please needs to open its pull request and why it is safe here, sends the first release through that pull request instead of a hand-pushedv1.0.0tag (the two would collide), and says to removerelease-asoncev1.0.0is tagged.android_release_setup_test.dartguards thatrelease-as, when set, is a plain version, and that the docs name both steps.The repository setting itself is left to the maintainer.
Closes #211