@pourkit/cli 0.0.0-next-20260617232425 → 0.0.0-next-20260618005759
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -9,9 +9,15 @@ Decide release intent and manage `.changeset/*.md` files during `promote-release
|
|
|
9
9
|
|
|
10
10
|
## Decision Rules
|
|
11
11
|
|
|
12
|
+
### Required Promotion Coverage
|
|
13
|
+
|
|
14
|
+
During `promote-release`, every Promotion PR requires a `.changeset/*.md` file in the PR diff except Development Release Branch to Stable Release Branch promotion. Existing historical Changesets outside the promoted diff do not count as coverage.
|
|
15
|
+
|
|
16
|
+
Create a catch-up Changeset when the promotion policy requires coverage and the promoted diff lacks `.changeset/*.md`, even if the change is mostly internal. If the release intent is unclear, stop and ask; do not open a Promotion PR that will fail the required Changeset check.
|
|
17
|
+
|
|
12
18
|
### User-Facing Changes
|
|
13
19
|
|
|
14
|
-
|
|
20
|
+
Use user-facing Changeset prose for work that users of the published CLI can observe:
|
|
15
21
|
|
|
16
22
|
- CLI commands, flags, arguments, outputs, prompts, errors, exit behavior, or generated files.
|
|
17
23
|
- Configuration shape, defaults, validation, target behavior, or workflow outcomes.
|
|
@@ -27,7 +33,7 @@ Skip a Changeset for mundane `chore`, `test`, `docs`, `build`, CI, and internal-
|
|
|
27
33
|
- One-off topic branches targeting the Integration Branch: do not create a Changeset; defer release notes to `promote-release`.
|
|
28
34
|
- Child issue topic branches targeting a PRD Branch: do not create a Changeset; the final PRD promotion handles release notes.
|
|
29
35
|
- PRD Branch to Integration Branch promotion: add one summarized product-increment Changeset. This flow is handled by `promote-release`, which requires a Changeset.
|
|
30
|
-
- Integration Branch to Development Release Branch promotion:
|
|
36
|
+
- Integration Branch to Development Release Branch promotion: ensure the Promotion PR diff contains `.changeset/*.md`; create a catch-up Changeset when the promoted diff lacks one. This flow is handled by `promote-release`, which requires a Changeset.
|
|
31
37
|
- Development Release Branch to Stable Release Branch promotion: do not add a Changeset. This is the only `promote-release` path where a Changeset is not needed.
|
|
32
38
|
- Hotfix topic branches targeting the Stable Release Branch: create a Changeset only when handled through `promote-release`; otherwise defer to the promotion path.
|
|
33
39
|
- Hotfix reconciliation forward through release lanes: verify the hotfix Changeset is present in the promoted diff. This flow is handled by `promote-release`, which requires a Changeset.
|
|
@@ -46,11 +52,12 @@ When unsure between `patch` and `minor`, choose the smallest version intent that
|
|
|
46
52
|
|
|
47
53
|
1. Confirm the current work is a `promote-release` flow. If not, do not author a Changeset.
|
|
48
54
|
2. Inspect the promoted diff, target branch, and PR purpose.
|
|
49
|
-
3.
|
|
50
|
-
4.
|
|
51
|
-
5. If a Changeset is
|
|
52
|
-
6.
|
|
53
|
-
7.
|
|
55
|
+
3. Apply promotion policy first: every `promote-release` mode except Development Release Branch to Stable Release Branch promotion requires `.changeset/*.md` in the PR diff.
|
|
56
|
+
4. Do not treat past Changesets outside the promoted diff as coverage.
|
|
57
|
+
5. If a required Changeset is missing from the promoted diff, create a single focused file under `.changeset/`.
|
|
58
|
+
6. If no Changeset is needed because this is Development Release Branch to Stable Release Branch promotion, document why in the PR summary when useful.
|
|
59
|
+
7. Keep the summary user-facing and final-state oriented.
|
|
60
|
+
8. Review that the package name and bump type are correct.
|
|
54
61
|
|
|
55
62
|
For PRD Branch to Integration Branch promotion, derive the summarized Changeset from the final product increment and current PRD context only. Do not copy child PR chronology, previous release notes, or prior Promotion PR text. This Changeset is required because final PRD PRs use `promote-release`.
|
|
56
63
|
|
|
@@ -73,4 +80,5 @@ Do not run `npx changeset publish`, `npm run changeset:publish`, or `changeset p
|
|
|
73
80
|
- The bump type matches the user impact.
|
|
74
81
|
- The prose describes the released behavior, not implementation chronology.
|
|
75
82
|
- Internal-only work does not invent release notes unless it is flowing through `promote-release` outside Development Release Branch to Stable Release Branch promotion, where a Changeset is required by workflow policy.
|
|
83
|
+
- Required `promote-release` Changesets appear in the actual Promotion PR diff; historical Changesets outside that diff do not count.
|
|
76
84
|
- Non-promote-release PRs do not author Changesets; `promote-release` PRs have a Changeset except Development Release Branch to Stable Release Branch promotion.
|
|
@@ -44,8 +44,11 @@ Fetch the latest remote refs and verify both source and target are the intended
|
|
|
44
44
|
### 3. Check Changeset Coverage
|
|
45
45
|
|
|
46
46
|
- Every `promote-release` PR requires a `.changeset/*.md` file in the promoted diff except Development Release Branch to Stable Release Branch promotion. Do not use `no-changeset-needed` with this skill.
|
|
47
|
+
- Coverage means the Promotion PR diff against the target branch contains a `.changeset/*.md` file. Do not treat historical Changesets already present elsewhere in the repository, on the target branch, or outside the promoted source-to-target diff as coverage.
|
|
48
|
+
- Before opening the PR, after creating the promotion branch and merging the source branch, check the PR diff with `git diff --name-only <target-branch>...HEAD -- .changeset/`. For every mode except Development Release Branch to Stable Release Branch promotion, this must report at least one `.changeset/*.md` file.
|
|
49
|
+
- If a required promotion diff contains no `.changeset/*.md` file, create a single catch-up Changeset on the promotion branch. If the release intent is unclear, stop and ask; do not open a Promotion PR that will fail the required Changeset check.
|
|
47
50
|
- For PRD Branch to Integration Branch promotion, add one summarized product-increment Changeset derived from the final PRD diff plus current PRD context. Do not copy child PR chronology, previous release notes, or prior Promotion PR text.
|
|
48
|
-
- For Integration Branch to Development Release Branch promotion,
|
|
51
|
+
- For Integration Branch to Development Release Branch promotion, use any `.changeset/*.md` files already present in the promoted diff as coverage. If the promoted diff contains none, create the catch-up Changeset before opening the PR.
|
|
49
52
|
- For Development Release Branch to Stable Release Branch promotion, do not add a Changeset. This stable promotion is the only no-Changeset path in `promote-release`.
|
|
50
53
|
- For hotfix reconciliation between release lane roles, verify the hotfix Changeset is present in the promoted diff. If it is not, stop and explain the process failure.
|
|
51
54
|
|
|
@@ -90,5 +93,5 @@ pourkit pr merge <number> --method merge
|
|
|
90
93
|
- Use `secret-commit-guard` before commit, push, and PR creation steps.
|
|
91
94
|
- Never publish locally with `changeset publish`, `npx changeset publish`, or npm publish commands.
|
|
92
95
|
- Never direct-push to configured lane branches.
|
|
93
|
-
-
|
|
96
|
+
- Before `pourkit pr create`, confirm the Promotion PR diff contains `.changeset/*.md` for every `promote-release` mode except Development Release Branch to Stable Release Branch promotion. Do not use `no-changeset-needed` with this skill.
|
|
94
97
|
- Do not invent Changesets during Development Release Branch to Stable Release Branch promotion. It is the only no-Changeset promote-release mode.
|