@cratis/pi 7.125.1 → 7.125.2
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.
package/package/corpus/skills/cratis-commits-and-pull-requests/references/pr-labels-and-release.md
CHANGED
|
@@ -43,11 +43,17 @@ Where the repository requires release intent, `no-release` is a decision, not an
|
|
|
43
43
|
|
|
44
44
|
This covers, whenever the PR touches *only* these:
|
|
45
45
|
|
|
46
|
-
- **Documentation**: anything under `Documentation/**`, READMEs, the `.cratis/ai/`
|
|
46
|
+
- **Documentation**: anything under `Documentation/**`, READMEs, the `.cratis/ai/` copy installed in a consumer repository.
|
|
47
47
|
- **CI and repository automation**: `.github/workflows/**`, `.github/scripts/**`, `.github/CODEOWNERS`, issue/PR templates.
|
|
48
48
|
- **Tests and specs**: `*.Specs/**`, `when_*/**`, `for_*/**`, `Integration/**`, and test-only fixtures.
|
|
49
49
|
- **Build and tooling configuration** that produces no shipped artifact difference: lint config, editor config, local scripts.
|
|
50
50
|
|
|
51
|
+
**In Cratis/AI the corpus is the product.** Its skills, rules, prompts and hooks reach users through `@cratis/pi`, so a corpus change there is labelled by its effect on those users, like code:
|
|
52
|
+
|
|
53
|
+
- `patch`: a fix to existing guidance, for example correcting a wrong command or a broken link in a skill.
|
|
54
|
+
- `minor`: new or changed guidance, for example a new skill or a new required step in an existing one.
|
|
55
|
+
- `no-release`: only when users cannot see the change, for example specs, evaluations or CI.
|
|
56
|
+
|
|
51
57
|
The test is **outward-facing effect, not file location**. A change under `Source/**` that only touches specs is not shippable; a one-line change to a published package's behavior is, however small. If a consumer could not tell the difference by upgrading, there is nothing to version. When genuinely unsure, ask rather than defaulting to `patch`: an unnecessary release is not free. It burns a version number, ships release notes describing nothing, and buries the releases that matter.
|
|
52
58
|
|
|
53
59
|
A non-release pull request must satisfy the relevant required checks like any other. Confirm label acceptance and publication suppression against the current workflow contract; do not assume external CI or API state.
|