Repository navigation
Release v0.2.0 - #8
Merged
Merged
Conversation
Contributor
|
Preview of 2c1004f: https://release-v0-2-0.ream-bqb.pages.dev |
Merged
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.
Raises the version to 0.2.0 with its changelog, and adds how each release gets one.
0.2.0 changelog
yarn releaseor the Prepare release workflow, and used as the release notesRelease tooling
CHANGELOG.md: one section per version (0.1.0 written by hand).yarn release patch|minor|major(scripts/release.ts prepare): raises the version from the latest tag and writes its section from the pull requests merged intodevsince then (titles and links; earlier releases andrelease/branches skipped).checkon pull requests intomainalso fails when the version has no changelog section.release.ts notes) instead of generated notes..github/workflows/prepare-release.yml: Actions → Prepare release does the same ondevand opens the release pull request intodev. It needs aRELEASE_TOKENsecret (fine-grained, this repo, Contents and Pull requests read and write) forcheckand the preview to run on that pull request, and it shows in Actions only once it is onmain.docs/deploy.md,CONTRIBUTING.md, AGENTS.md.Checked
prepareonce (0.2.0), twice (refused), andcheckwith and without a section.dev, apart from the push and the pull request.After merging, open
devintomainto release.