@kaisers-io/refs 0.19.0 → 0.19.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/CHANGELOG.md +59 -22
- package/README.md +1 -1
- package/dist/refs.mjs +110 -108
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,65 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [0.19.2] - 2026-11-21
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- **The bundled `minimatch` moves from 11.0.5 to 11.0.9.** 11.0.7 removes a quadratic compile time
|
|
13
|
+
for long wildcard patterns, a regression introduced in 11.0.0; refs compiles the workspace
|
|
14
|
+
patterns read from a checkout, and a checkout is third-party content. No advisory was published
|
|
15
|
+
for it. The bundled `commander` moves from 15.0.0 to 15.1.0, a release of parser fixes.
|
|
16
|
+
|
|
17
|
+
## [0.19.1] - 2026-11-08
|
|
18
|
+
|
|
19
|
+
### Security
|
|
20
|
+
|
|
21
|
+
- **Development installs resolve from the public npm registry, and stop on an unsupported Node.**
|
|
22
|
+
The root `.npmrc` now pins `registry=https://registry.npmjs.org/`, so a user-level default
|
|
23
|
+
registry such as a company mirror no longer decides where installs in this repository resolve,
|
|
24
|
+
which trust-policy evidence and advisories they see, or which tarball URLs reach the lockfile. A
|
|
25
|
+
user-level registry for a single scope (`@scope:registry=`) still applies to that scope.
|
|
26
|
+
Its two previous settings were not read by pnpm 12, which takes only auth, registry, TLS and
|
|
27
|
+
proxy settings from `.npmrc`. They now live in `pnpm-workspace.yaml` as `saveExact` and
|
|
28
|
+
`engineStrict`, so `pnpm add` writes exact versions again and `pnpm install --frozen-lockfile`
|
|
29
|
+
fails on a Node outside `engines.node`. The published CLI is unchanged.
|
|
30
|
+
|
|
31
|
+
### Changed
|
|
32
|
+
|
|
33
|
+
- **A re-run release job can no longer move the GitHub Latest release backwards.** The job that
|
|
34
|
+
creates the GitHub release used to leave Latest to the API, which makes every new release Latest.
|
|
35
|
+
Re-running a failed one for an older version after a newer release had shipped would therefore
|
|
36
|
+
have marked the older version Latest. It now compares the tag with the current Latest release
|
|
37
|
+
and always states the decision, and release entries for different tags are created one at a
|
|
38
|
+
time.
|
|
39
|
+
|
|
40
|
+
- **Every release is now installed from npm on Linux, macOS and Windows after it is published.**
|
|
41
|
+
The release workflow used to test only a tarball it packed itself, on Linux, while the package it
|
|
42
|
+
published was assembled separately and never installed. A new job waits until the registry serves
|
|
43
|
+
the version, installs it the way a user does, and runs the same smoke test that pull requests now
|
|
44
|
+
run on all three platforms: add, list, sync, resolve and remove of a local repository, each
|
|
45
|
+
outcome checked. It runs after publication and cannot stop a release; `CONTRIBUTING.md` says what
|
|
46
|
+
to do when it fails.
|
|
47
|
+
|
|
48
|
+
### Documentation
|
|
49
|
+
|
|
50
|
+
- **`refs edit --remove`, `--decline` and `--undecline` are in the command references.**
|
|
51
|
+
`docs/commands.md` lacked all three and the skill's `COMMANDS.md` lacked `--remove`, although
|
|
52
|
+
they shipped in 0.13.1 and 0.14.0. Both now give the synopsis, the `--json` data each mode
|
|
53
|
+
returns, and its exit codes. A test now fails when a registered command or option is missing
|
|
54
|
+
from either reference.
|
|
55
|
+
|
|
56
|
+
- **The README says how to upgrade.** A new `Upgrading` section gives the commands that move the
|
|
57
|
+
CLI and the skill (or the Codex plugin) to a new release together, notes that a global skill
|
|
58
|
+
install needs `-g` again, and points at `refs doctor` and the changelog for what follows.
|
|
59
|
+
`docs/install.md` and the npm package README link to it.
|
|
60
|
+
|
|
61
|
+
- **`SECURITY.md` is the policy again, and the security model has its own page.** The reporting
|
|
62
|
+
process, supported versions and scope lists stay in `SECURITY.md`, which GitHub shows as the
|
|
63
|
+
repository's security policy. The account of the git processes refs starts, of configured hooks,
|
|
64
|
+
filters and `core.fsmonitor`, and of untrusted checkout content moved unchanged to
|
|
65
|
+
`docs/security.md`. A report now names what a useful one contains.
|
|
66
|
+
|
|
8
67
|
## [0.19.0] - 2026-11-07
|
|
9
68
|
|
|
10
69
|
### Security
|
|
@@ -1918,25 +1977,3 @@ trusted-publishing pipeline end to end.
|
|
|
1918
1977
|
URL-carrying message, and read-only enforcement of managed checkouts via
|
|
1919
1978
|
installed git hooks.
|
|
1920
1979
|
- Agent skill (`skills/refs/`) documenting the investigate/add/maintain workflows.
|
|
1921
|
-
|
|
1922
|
-
[Unreleased]: https://github.com/kaisers-io/refs/compare/v0.12.0...HEAD
|
|
1923
|
-
[0.12.0]: https://github.com/kaisers-io/refs/compare/v0.11.0...v0.12.0
|
|
1924
|
-
[0.11.0]: https://github.com/kaisers-io/refs/compare/v0.10.0...v0.11.0
|
|
1925
|
-
[0.10.0]: https://github.com/kaisers-io/refs/compare/v0.9.0...v0.10.0
|
|
1926
|
-
[0.9.0]: https://github.com/kaisers-io/refs/compare/v0.8.3...v0.9.0
|
|
1927
|
-
[0.8.3]: https://github.com/kaisers-io/refs/compare/v0.8.2...v0.8.3
|
|
1928
|
-
[0.8.2]: https://github.com/kaisers-io/refs/compare/v0.8.1...v0.8.2
|
|
1929
|
-
[0.8.1]: https://github.com/kaisers-io/refs/compare/v0.8.0...v0.8.1
|
|
1930
|
-
[0.8.0]: https://github.com/kaisers-io/refs/compare/v0.7.0...v0.8.0
|
|
1931
|
-
[0.7.0]: https://github.com/kaisers-io/refs/compare/v0.6.1...v0.7.0
|
|
1932
|
-
[0.6.1]: https://github.com/kaisers-io/refs/compare/v0.6.0...v0.6.1
|
|
1933
|
-
[0.6.0]: https://github.com/kaisers-io/refs/compare/v0.5.1...v0.6.0
|
|
1934
|
-
[0.5.1]: https://github.com/kaisers-io/refs/compare/v0.5.0...v0.5.1
|
|
1935
|
-
[0.5.0]: https://github.com/kaisers-io/refs/compare/v0.4.0...v0.5.0
|
|
1936
|
-
[0.4.0]: https://github.com/kaisers-io/refs/compare/v0.3.0...v0.4.0
|
|
1937
|
-
[0.3.0]: https://github.com/kaisers-io/refs/compare/v0.2.0...v0.3.0
|
|
1938
|
-
[0.2.0]: https://github.com/kaisers-io/refs/compare/v0.1.3...v0.2.0
|
|
1939
|
-
[0.1.3]: https://github.com/kaisers-io/refs/compare/v0.1.2...v0.1.3
|
|
1940
|
-
[0.1.2]: https://github.com/kaisers-io/refs/compare/v0.1.1...v0.1.2
|
|
1941
|
-
[0.1.1]: https://github.com/kaisers-io/refs/compare/v0.1.0...v0.1.1
|
|
1942
|
-
[0.1.0]: https://github.com/kaisers-io/refs/releases/tag/v0.1.0
|
package/README.md
CHANGED
|
@@ -61,7 +61,7 @@ The `npm:` prefix says which registry the name belongs to, so a package and a re
|
|
|
61
61
|
|
|
62
62
|
## Driving the CLI yourself
|
|
63
63
|
|
|
64
|
-
The agent runs these. Typing one yourself is quicker for some of them, and `refs sync` is the one most people reach for. `refs doctor` is the one to run after updating refs: the CLI and the skill each carry a version, and it says when they have drifted apart.
|
|
64
|
+
The agent runs these. Typing one yourself is quicker for some of them, and `refs sync` is the one most people reach for. `refs doctor` is the one to run after updating refs: the CLI and the skill each carry a version, and it says when they have drifted apart. [Upgrading](https://github.com/kaisers-io/refs#upgrading) has the commands that move both.
|
|
65
65
|
|
|
66
66
|
```bash
|
|
67
67
|
# clones and proposes; nothing is configured yet
|