rlsbl 0.121.4 → 0.121.5

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.
Files changed (2) hide show
  1. package/README.md +4 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,4 +1,4 @@
1
- <!-- Auto-generated by selfdoc from docs/_README.md — do not edit -->
1
+ <!-- Auto-generated by selfdoc from .stricttools/docs/_README.md — do not edit -->
2
2
 
3
3
  <p align="center">
4
4
  <img src="logo.svg" alt="rlsbl" width="336" height="105">
@@ -123,7 +123,7 @@ release branch and `rlsbl release resume` completes the *same* version; a failed
123
123
  release never burns it.
124
124
 
125
125
  The step-by-step pipeline, including what each step does in monorepo and releasable
126
- mode, is in [docs/release-workflow.md](docs/release-workflow.md).
126
+ mode, is in [.stricttools/docs/release-workflow.md](.stricttools/docs/release-workflow.md).
127
127
 
128
128
  Use `--dry-run` to preview without changes: mutating operations are recorded and printed as a
129
129
  would-do log rather than performed. A small set of commands declares itself `consequential`
@@ -175,7 +175,7 @@ Created files are committed automatically by default.
175
175
  - `.github/workflows/ci-custom.yml` -- runs alongside `ci.yml`
176
176
  - `.github/workflows/publish-custom.yml` -- runs alongside `publish.yml`
177
177
 
178
- See [docs/ci-customization.md](docs/ci-customization.md) for an example.
178
+ See [.stricttools/docs/ci-customization.md](.stricttools/docs/ci-customization.md) for an example.
179
179
 
180
180
  **Runs config migrations** when `.rlsbl/config-schema.json` exists.
181
181
 
@@ -198,7 +198,7 @@ Checks are grouped by tag -- `--tag` runs one family, `--name` runs a single che
198
198
  | `maven` | 1 |
199
199
  | (untagged) | 4 |
200
200
 
201
- What each tag's checks actually verify, one row per check with its severity, is in [docs/checks.md](docs/checks.md), which also says which tags the release pipeline runs on its own.
201
+ What each tag's checks actually verify, one row per check with its severity, is in [.stricttools/docs/checks.md](.stricttools/docs/checks.md), which also says which tags the release pipeline runs on its own.
202
202
 
203
203
  ```
204
204
  rlsbl check --all # run all checks
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "rlsbl",
3
- "version": "0.121.4",
3
+ "version": "0.121.5",
4
4
  "description": "Release orchestration and project scaffolding CLI that bumps versions, validates a structured JSONL changelog, tags only the commit CI verified, and publishes to npm, PyPI, Go and more",
5
5
  "homepage": "https://smmh.dev/rlsbl/",
6
6
  "license": "MIT",