Repository navigation
Release 0.3.0 - #19
Merged
Merged
Conversation
Follows the release process in justintout/systemone: the tag is the result of a release, not the trigger. A maintainer runs Release on main. It runs the tests, checks that pubspec.yaml holds an untagged version with a CHANGELOG.md entry, and validates the package. Only then does it tag and create the GitHub release. pub.dev only publishes from a workflow started by a tag push, and a tag pushed with GITHUB_TOKEN starts no workflows. The tag is pushed with a deploy key so that publish.yml still runs.
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
1 participant
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.
Bumps the version to 0.3.0, adds the CHANGELOG entry for #17 and #18, and adds a Release workflow that follows the process in justintout/systemone.
The tag is the result of a release, not the trigger. After this merges, run Release from the Actions tab on
main. It runs the tests, then checks thatpubspec.yamlholds a version that isn't tagged yet, thatCHANGELOG.mdhas an entry for it, and thatdart pub publish --dry-runpasses. Only then does it push an annotatedv0.3.0tag and create the GitHub release from the CHANGELOG section. The tag push startspublish.yml, which publishes to pub.dev.Differences from systemone:
GITHUB_TOKENstarts no workflows, so the tag is pushed with a deploy key (RELEASE_DEPLOY_KEY). The workflow fails early if the secret is missing.pubspec.yaml, so the release PR sets it. There is no bump input.apidiff.Before the first run:
RELEASE_DEPLOY_KEYsecret.release tagsruleset like systemone's, which blocks updating or deletingv*tags.Don't push a
v*tag by hand. That publishes a version no check has seen.