Repository navigation
chore(ci): automate releases with uppt release PRs - #118
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
Merged
This branch was successfully deployed
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.
Replaces the laptop-driven changelogen release flow with uppt, the release automation used by nuxt/nuxt and nuxt/image, and retires the
nextbranch model in favour of trunk-based development.What changes
release.ymlnow implements the uppt flow: every push tomainopens or updates a draft release PR; merging it tags the squash commit, creates the GitHub release from the PR body, and stages an npm publish via OIDC trusted publishing. Thepackjob handles checkout and install itself becauseprepackneedspnpm run dev:preparefirst (same as the pkg.pr.new workflow).ci.ymlandpkg-pr-new.ymldrop theirnexttriggers; previews now build on PRs and pushes tomain.release/release:nextscripts removed frompackage.json.main.Follow-ups after merge
nexttomain, then delete thenextbranch.npm,npm stage publishpermission).npmenvironment (scoped tov*tags) and the "allow Actions to create PRs" setting are already in place.Prereleases for v7 stay manual for now; see RELEASING.md.