Commits on Aug 14, 2026

1. feat: fork and onboard @unabandoned/JSONStream (vendor through, node:… …

   …test suite) (#1)
   
   Adopts JSONStream into the `unabandoned` program. JSONStream is
   unmaintained (last release 2018) and shipped the abandoned `through`
   runtime dependency, so per the org directive (abandoned + any outdated
   dep → fork and own; fix forward, don't pin) it's a fork/own target. This
   is the standard `@unabandoned` onboarding plus a fix-forward cleanup of
   its tree.
   
   Tracking issue: unabandoned/browser-pack#3
   
   ## Tree cleanup (fix forward)
   
   - **`through` → vendored.** `through` is abandoned. It has zero deps of
   its own and JSONStream's `parse()`/`stringify()` streams are built
   directly on its `queue()`/`write()`/`end()` surface, so it's inlined
   verbatim at `lib/through.js` (MIT header preserved) and the external
   dependency is dropped. Behaviour is identical.
   - **`jsonparse` kept.** Zero-dep leaf, still current — kept as the sole
   runtime dependency, pinned exactly so Renovate tracks it.
   
   Runtime dependency tree after this change: `@unabandoned/JSONStream →
   jsonparse` (one leaf, no abandoned deps).
   
   ## Test suite → `node:test`
   
   The upstream suite depended on a heavy, abandoned dev tree (`tape`,
   `it-is`, `assertions`, `render`, `trees`, `event-stream`). It's ported
   to `node:test` + `node:assert` with a near-zero dev tree:
   
   - tape-based files reuse the shared `tap-adapter` shim.
   - The `it-is` / `process.on('exit')` scripts become explicit `node:test`
   cases.
   - Round-trip tests use a small local `event-stream` shim
   (`readArray`/`writeArray`/`connect`) instead of the abandoned package.
   - `test/run.js` (bespoke runner) and the dead `gen.js` stress script are
   removed.
   
   Only `@commitlint/*` remains in `devDependencies`.
   
   ## Onboarding
   
   - Re-scoped to `@unabandoned/JSONStream`; repo/bugs/homepage URLs
   updated; `engines.node` set to `>=22.12`.
   - Thin reusable-workflow callers pinned to `unabandoned/.github` (ci,
   codeql, commitlint, publish, release-please, release-cut,
   release-security, scorecard, renovate-config).
   - `renovate.json` (extends shared preset, `forkProcessing` enabled),
   release-please config/manifest, commitlint config + commit-msg githook,
   `.npmrc`, `.gitignore`.
   - `.unabandoned.yml` dashboard metadata listing the four consumers
   (module-deps, deps-sort, insert-module-globals, browser-pack).
   
   ## Verification
   
   `node --test test/*.js` — **28 tests, 28 pass, 0 fail** on Node 22.22
   and Node 24.19 (exit 0 on both). Metadata validated with
   `scripts/validate_metadata.py` from `unabandoned/.github`.
   
   Once this releases and publishes, the four consumer forks repoint their
   `JSONStream` dependency to `npm:@unabandoned/JSONStream@^1` (separate
   PRs), removing JSONStream from browserify's transitive tree.
   
   ---
   _Generated by [Claude
   Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_

   

   00o-sh authored Aug 14, 2026
   Configuration menu

   • View commit details
   • Copy full SHA for f11ffef
   • Browse repository at this point

   Copy the full SHA

   f11ffef View commit details

   Browse the repository at this point in the history

2. fix: lowercase npm package name to @unabandoned/jsonstream (#4) …

   Follow-up to #1. The onboarding merged with the package named
   `@unabandoned/JSONStream`, but **npm forbids uppercase letters in new
   package names** — that name can't be published, and it can't even be
   resolved as an `npm:` alias (npm fails name validation with _"name can
   no longer contain capital letters"_, which is exactly what broke `npm
   install` in the first repoint PR).
   
   This renames the published package to the lowercase
   **`@unabandoned/jsonstream`**.
   
   What does **not** change:
   - The GitHub repo stays `unabandoned/JSONStream`.
   - Consumers keep the dependency **key** `JSONStream`, aliased to
   `npm:@unabandoned/jsonstream@^1`, so `node_modules/JSONStream` and
   `require('JSONStream')` are unchanged — no consumer code changes.
   - The `JSONStream.parse` / `JSONStream.stringify` API is untouched.
   
   Also updates `package` in `.unabandoned.yml` to match (validated).
   
   `node --test test/*.js` still passes (28/28) — the rename is inert to
   behaviour.
   
   ---
   _Generated by [Claude
   Code](https://claude.ai/code/session_01Wa4Hra9ctCDzbpPUaQB9mG)_

   

   00o-sh authored Aug 14, 2026
   Configuration menu

   • View commit details
   • Copy full SHA for 76dfce6
   • Browse repository at this point

   Copy the full SHA

   76dfce6 View commit details

   Browse the repository at this point in the history

3. chore(master): release jsonstream 1.4.0 (#5) …

   🤖 I have created a release *beep* *boop*
   ---
   
   
   ##
   [1.4.0](unabandoned/JSONStream@jsonstream-v1.3.5...jsonstream-v1.4.0)
   (2026-08-14)
   
   
   ### Features
   
   * add option for emitting keys
   ([9aa2446](unabandoned@9aa2446))
   * fork and onboard @unabandoned/JSONStream (vendor through, node:test
   suite) ([#1](unabandoned#1))
   ([f11ffef](unabandoned@f11ffef))
   
   
   ### Bug Fixes
   
   * lowercase npm package name to @unabandoned/jsonstream
   ([#4](unabandoned#4))
   ([76dfce6](unabandoned@76dfce6))
   
   ---
   This PR was generated with [Release
   Please](https://github.com/googleapis/release-please). See
   [documentation](https://github.com/googleapis/release-please#release-please).

   

   00o-sh authored Aug 14, 2026
   Configuration menu

   • View commit details
   • Copy full SHA for 3fe406c
   • Browse repository at this point

   Copy the full SHA

   3fe406c View commit details

   Browse the repository at this point in the history