You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **Note on workflow naming:**`release-please.yml` is named after a tool we evaluated but didn't adopt — it actually runs the Changesets CLI. A rename to `changeset-version.yml` is tracked in [dvflw/mantle#123](https://github.com/dvflw/mantle/issues/123).
32
-
33
31
## Step 1: Add a Changeset (During Development)
34
32
35
33
Every PR that changes user-visible behavior needs a changeset. Run this from the repo root:
@@ -56,7 +54,7 @@ If a PR touches only CI, tests, or tooling with no user impact, skip the changes
56
54
57
55
## Step 2: The Version PR
58
56
59
-
After any push to `main` that contains pending changesets, the `release-please.yml` workflow automatically creates (or updates) a PR titled **"ci: version packages"**.
57
+
After any push to `main` that contains pending changesets, the `changeset-version.yml` workflow automatically creates (or updates) a PR titled **"ci: version packages"**.
60
58
61
59
This PR:
62
60
- Bumps `version` in each affected `package.json` (taking the highest bump across all pending changesets)
@@ -65,7 +63,7 @@ This PR:
65
63
66
64
Review the PR to confirm the version bumps and changelog entries are correct. If more changesets land on `main` before you merge, CI updates the PR automatically.
67
65
68
-
> **Loop guard:** the workflow has an `if` condition that skips runs where the triggering commit message starts with `"ci: version packages"`. This prevents the workflow from retriggering on its own Version PR merge commit. If you ever rename the commit message in the workflow, update the guard condition in `release-please.yml` to match.
66
+
> **Loop guard:** the workflow has an `if` condition that skips runs where the triggering commit message starts with `"ci: version packages"`. This prevents the workflow from retriggering on its own Version PR merge commit. If you ever rename the commit message in the workflow, update the guard condition in `changeset-version.yml` to match.
69
67
70
68
## Step 3: Merge the Version PR
71
69
@@ -107,7 +105,7 @@ The tag-triggered workflows are safe to retrigger — goreleaser will fail clean
107
105
108
106
This applies when `package.json` is already at the target version but `.changeset/` contains no pending changeset files — for example, the first-ever release of a newly bootstrapped repo, or after manually editing `package.json` outside the changeset flow.
109
107
110
-
In this state the `release-please.yml` workflow has nothing to process and will not create a Version PR. Push the tags directly:
108
+
In this state the `changeset-version.yml` workflow has nothing to process and will not create a Version PR. Push the tags directly:
0 commit comments