okf-kit 0.17.0 → 0.17.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/CHANGELOG.md +6 -0
- package/README.md +1 -1
- package/docs/ci.md +1 -1
- package/package.json +1 -1
- package/templates/okf-staleness.yml +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.17.1] - 2026-10-05
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- The `templates/okf-staleness.yml` pin (install line and header) is now rewritten to the release version by `scripts/bump-okf-kit-pin.mjs` at each release cut, so it no longer needs a manual bump. The script also re-syncs the header of this repo's generated copy `.github/workflows/okf-staleness.yml` and fails before writing when the template lacks exactly one install pin and one header. For consumers: the template shipped in 0.17.0 still pinned okf-kit 0.16.0; the 0.17.1 template pins the release that ships it.
|
|
15
|
+
|
|
10
16
|
## [0.17.0] - 2026-10-03
|
|
11
17
|
|
|
12
18
|
### Added
|
package/README.md
CHANGED
|
@@ -73,7 +73,7 @@ Pin the exact version and use a full (non-shallow) checkout; [CI usage](docs/ci.
|
|
|
73
73
|
with:
|
|
74
74
|
fetch-depth: 0
|
|
75
75
|
- name: OKF bundle check
|
|
76
|
-
run: npx okf-kit@0.17.
|
|
76
|
+
run: npx okf-kit@0.17.1 check path/to/bundle
|
|
77
77
|
```
|
|
78
78
|
|
|
79
79
|
## Documentation
|
package/docs/ci.md
CHANGED
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
|
|
13
13
|
Pin the version: an unpinned `npx okf-kit` picks up new rules on their release day, which turns an unrelated PR red.
|
|
14
14
|
|
|
15
|
-
Releasing a new okf-kit version to npm must also bump the `npm install -g okf-kit@<version>` pins this repo's own `orchestrator-workflow` package carries in `.github/workflows/`, in the same release commit; see `CONTRIBUTING.md`'s "Releasing okf-kit" section for the order.
|
|
15
|
+
Releasing a new okf-kit version to npm must also bump the `npm install -g okf-kit@<version>` pins this repo's own `orchestrator-workflow` package carries in `.github/workflows/`, in the same release commit. `scripts/bump-okf-kit-pin.mjs` rewrites those pins and also the install pin and the "pinned to okf-kit" header sentence in `templates/okf-staleness.yml`, so the shipped template always names the release that ships it (it exits non-zero, before writing anything, if the template is missing or lacks exactly one of each); see `CONTRIBUTING.md`'s "Releasing okf-kit" section for the order.
|
|
16
16
|
|
|
17
17
|
## Warn-only staleness workflow template
|
|
18
18
|
|
package/package.json
CHANGED
|
@@ -3,7 +3,7 @@ name: OKF staleness
|
|
|
3
3
|
# GENERATED FROM THE OKF-KIT TEMPLATE `templates/okf-staleness.yml` of the
|
|
4
4
|
# okf-kit package (LanNguyenSi/agent-dx, packages/okf-kit; the template
|
|
5
5
|
# first ships in the okf-kit release after 0.16.0), pinned to okf-kit
|
|
6
|
-
# 0.
|
|
6
|
+
# 0.17.1 below. Do not hand-edit this file outside the lines marked
|
|
7
7
|
# "REPO-SPECIFIC": re-sync it from the template whenever the pin moves.
|
|
8
8
|
# A repo that deviates documents the deviation in a comment block at the
|
|
9
9
|
# deviating spot, next to the REPO-SPECIFIC marker.
|
|
@@ -60,7 +60,7 @@ jobs:
|
|
|
60
60
|
# alone here. Move this pin deliberately, never as an automatic
|
|
61
61
|
# upgrade, and record each move in the bundle's log.md together with
|
|
62
62
|
# the old and the new version's measured verdict on this bundle.
|
|
63
|
-
run: npm install -g okf-kit@0.
|
|
63
|
+
run: npm install -g okf-kit@0.17.1 --no-audit --no-fund
|
|
64
64
|
|
|
65
65
|
- name: Assert CLI is alive (output, not exit code)
|
|
66
66
|
shell: bash
|