@kaisers-io/refs 0.18.1 → 0.18.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.
Files changed (3) hide show
  1. package/CHANGELOG.md +27 -4
  2. package/dist/refs.mjs +204 -45
  3. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -5,6 +5,29 @@ 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.18.2] - 2026-10-13
9
+
10
+ ### Security
11
+
12
+ - **Bundled dependencies moved past known denial-of-service advisories.** `smol-toml` 1.8.0 →
13
+ 1.9.1 fixes quadratic-time parsing ([GHSA-r4xh-jqrq-34v2](https://github.com/advisories/GHSA-r4xh-jqrq-34v2));
14
+ refs parses `config.toml` with it. `brace-expansion` 5.0.9 → 5.0.12, reached through
15
+ `minimatch`, fixes unbounded recursion and quadratic expansion
16
+ ([GHSA-qhr7-859c-m2p7](https://github.com/advisories/GHSA-qhr7-859c-m2p7),
17
+ [GHSA-6j4f-fj2g-mc7p](https://github.com/advisories/GHSA-6j4f-fj2g-mc7p),
18
+ [GHSA-q2hr-2g5m-vwhr](https://github.com/advisories/GHSA-q2hr-2g5m-vwhr)); refs matches
19
+ workspace patterns read from a checkout with it, and a checkout is third-party content. `zod`
20
+ 4.6.2 → 4.6.7. All three are bundled into the published CLI.
21
+
22
+ ### Changed
23
+
24
+ - **An invalid `config.toml` is reported in the new parser's words.** The message still carries
25
+ only the fault and its position, never a line of the file, but the fault is named differently
26
+ and the column points at the offending character rather than the start of the line.
27
+ - **Development moved to pnpm 12 and Node 24.21.** The development toolchain moved too: `oxlint`, `oxfmt`,
28
+ `vitest`, `vite`, `tsdown`, and `@types/node` within the 24 line. The published CLI has no pnpm
29
+ requirement of its own.
30
+
8
31
  ## [0.18.1] - 2026-09-20
9
32
 
10
33
  ### Changed
@@ -363,7 +386,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
363
386
  name up with plain bracket access, so a name absent from the record resolved up the prototype
364
387
  chain: `packages['toString']` answered with `Object.prototype.toString`, which is truthy and
365
388
  therefore looked registered. Measured with the built CLI: `refs tag <ref> 1.2.3 --package
366
- toString` returned a tag, silently using the ref's own format for a package the configuration
389
+ toString` returned a tag, silently using the ref's own format for a package the configuration
367
390
  does not have, and `refs resolve toString --ref <ref>` crashed.
368
391
 
369
392
  All four now ask whether the record has its own entry under that name, as their siblings already
@@ -812,7 +835,7 @@ can contain one — TOML has no escape for it — so this only affects a hand-bu
812
835
  Existing entries are untouched. A description imported from a manifest before this release stays
813
836
  exactly as it is — nothing distinguishes it from one written by hand, so nothing rewrites it. To
814
837
  review them: `refs show <ref> --packages --json`, and `refs edit <ref> --package <name>
815
- description "…"` to replace one.
838
+ description "…"` to replace one.
816
839
 
817
840
  ### Security
818
841
 
@@ -1163,7 +1186,7 @@ long it has been there.
1163
1186
  `checkout.status`, which answers the question `missing` was often assumed to.
1164
1187
 
1165
1188
  - **The "lock is held" error now says who holds it and for how long.** It used to read `lock <name>
1166
- is held — another refs process is running`, which left no way to tell a running `sync` from
1189
+ is held — another refs process is running`, which left no way to tell a running `sync` from
1167
1190
  something that crashed 90 seconds ago. It now names the recorded pid, whether that pid is still
1168
1191
  present, how long the lock has been held, and when it becomes reclaimable.
1169
1192
 
@@ -1690,7 +1713,7 @@ is held — another refs process is running`, which left no way to tell a runnin
1690
1713
  ### Added
1691
1714
 
1692
1715
  - `refs add` now emits progress lines on stderr while it works (`refs: resolving npm
1693
- package '…'…`, `refs: cloning …`, `refs: detecting workspace packages…`) in both
1716
+ package '…'…`, `refs: cloning …`, `refs: detecting workspace packages…`) in both
1694
1717
  human and `--json` mode, so long clones no longer look like a hang. stdout is
1695
1718
  unaffected and stays exactly the parseable envelope in `--json` mode.
1696
1719