rig-create 1.0.0 → 1.0.1
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/README.md +6 -0
- package/docs/CHECKS.md +17 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -31,6 +31,12 @@ bunx --package @rig-c/create rig-create interview --check p1 --json
|
|
|
31
31
|
bunx --package @rig-c/create rig-create next p1 --json
|
|
32
32
|
```
|
|
33
33
|
|
|
34
|
+
The convenience alias provides the short form:
|
|
35
|
+
|
|
36
|
+
```sh
|
|
37
|
+
bunx rig-create init p1
|
|
38
|
+
```
|
|
39
|
+
|
|
34
40
|
Or install it globally:
|
|
35
41
|
|
|
36
42
|
```sh
|
package/docs/CHECKS.md
CHANGED
|
@@ -1663,3 +1663,20 @@ optional on older records; present rows are validated by the writer and check.
|
|
|
1663
1663
|
| `PACKAGE_UPGRADE_CHECK_FAILED` | The project check could not complete; repair the record or installed packages and retry. |
|
|
1664
1664
|
| `PACKAGE_UPGRADE_REFUSAL` | The named package move adds or changes the named check finding; preserve the original pins and resolve that finding before retrying. |
|
|
1665
1665
|
| `PACKAGE_UPGRADE_CONFLICT` | Another package writer holds the lock, or a source changed during staging; finish the other write and retry against current bytes. |
|
|
1666
|
+
|
|
1667
|
+
## Release workflow gates
|
|
1668
|
+
|
|
1669
|
+
These CI-only codes name `.github/workflows/release.yml` or its tagged
|
|
1670
|
+
`package.json`; they do not validate project records.
|
|
1671
|
+
|
|
1672
|
+
| Code | Meaning and remedy |
|
|
1673
|
+
| --- | --- |
|
|
1674
|
+
| `RELEASE_REF_NOT_TAG` | `release.yml`: use a tag push or dispatch with matching `--ref vX.Y.Z -f tag=vX.Y.Z`. |
|
|
1675
|
+
| `RELEASE_TAG_FORM` | `release.yml`: supply a strict `vX.Y.Z` tag without prerelease or leading zeros. |
|
|
1676
|
+
| `RELEASE_TAG_UNRESOLVED` | `release.yml`: restore tag/API access so the explicit tag ref resolves to a full commit SHA. |
|
|
1677
|
+
| `PROVENANCE_SHA_MISMATCH` | `release.yml`: the run, API or fetched tag commits differ; inspect the cut tag and recover on that exact tag ref without moving it. |
|
|
1678
|
+
| `RELEASE_TAG_NOT_ON_MAIN` | `release.yml`: restore fetched main/tag history or land the reviewed release commit on main before cutting a new tag. |
|
|
1679
|
+
| `RELEASE_TAG_VERSION_MISMATCH` | Tagged `package.json`: release the exact `@rig-c/create@X.Y.Z` matching the tag; do not move an existing cut tag. |
|
|
1680
|
+
| `RELEASE_ALREADY_PUBLISHED` | `release.yml`: npm already serves the version; verify that publication rather than republishing it. |
|
|
1681
|
+
| `RELEASE_REGISTRY_UNCONFIRMED` | `release.yml`: confirmation of both names timed out; inspect npm before recovery because publication may already have succeeded. |
|
|
1682
|
+
| `ALIAS_SAME_CONTENT` | `scripts/alias_tarball.ts compare`: an alias differs beyond the `package/package.json` name line; rebuild it from the reviewed scoped tarball and resolve every named file difference before publication. |
|