atomic: 0.9.14 -> 0.9.15 - #2802
Merged
Merged
Conversation
Produced by pkgs/by-name/atomic/update.sh, which resolves the version from the registry's latest dist-tag, verifies the tarball against the registry's published sha512 integrity, re-derives npm-dist-repairs.patch against that tarball, and learns npmDepsHash from a build mismatch. The registry's latest dist-tag resolves to 0.9.15; the 0.9.15-alpha.1 upstream cut before it remains under the separate `next` tag, which the script does not read. The npm-dist-repairs.patch churn is the two mechanical repairs re-derived against the new shrinkwrap: ten @bastani/atomic-natives* integrity backfills, and the devDependencies removal. Checks run: nix build of checks.aarch64-darwin.package-atomic, package-atomic-test-help, and atomic-agent-environment-structural, plus prek (gitleaks, treefmt) over the three changed files. That selection is the whole of what this repository builds out of the atomic package definition — the two package checks cover the derivation and its versionCheckHook, and the structural regulator covers the extension selector lists the bump could invalidate. The rest of the flake's checks are not reachable from these three files, so a full `just check-fast` was deliberately left out as coverage disproportionate to the diff. versionCheckHook confirms the built binary reports 0.9.15. The surfaces this configuration binds to are unchanged across the two distributions: the CLI flag set in dist/cli and dist/cli.js is identical, and dist/cli.d.ts and dist/index-extensions.d.ts are byte-identical.
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Produced by
pkgs/by-name/atomic/update.sh, which resolves the version from the registry's latest dist-tag, verifies the tarball against the registry's published sha512 integrity, re-derivesnpm-dist-repairs.patchagainst that tarball, and learnsnpmDepsHashfrom a build mismatch. No value here was hand-written.The latest dist-tag resolves to
0.9.15; the0.9.15-alpha.1upstream cut before it remains under the separatenexttag (now0.9.16-alpha.1), which the script does not read.The
npm-dist-repairs.patchchurn is the two mechanical repairs re-derived against the new shrinkwrap: ten@bastani/atomic-natives*integrity backfills, and thedevDependenciesremoval.Consumer surfaces
Unchanged across
0.9.14..0.9.15: the CLI flag set acrossdist/clianddist/cli.jsis identical, anddist/cli.d.tsanddist/index-extensions.d.tsare byte-identical, so this configuration's flag and extension-API bindings are unaffected.Checks
nix buildofchecks.aarch64-darwin.package-atomic,package-atomic-test-help, andatomic-agent-environment-structural, plusprek(gitleaks, treefmt) over the three changed files. That selection is the whole of what this repository builds out of the atomic package definition — the two package checks cover the derivation and itsversionCheckHook, and the structural regulator covers the extension selector lists a bump could invalidate. The rest of the flake's checks are not reachable from these three files, so a fulljust check-fastwas deliberately left out as coverage disproportionate to the diff.versionCheckHookconfirms the built binary reports0.9.15.