Repository navigation
Update nickel-lsp to 1.18.0 - #1187
Conversation
|
Opened for review by pkgmgr auto-update (a freshness update; it clears no advisory). The leaf policy did not auto-approve it because:
To defer it, leave a comment rather than closing: a closed auto-update PR currently marks the package |
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
…1.18.0) cve-2026-111943-webpki-lock.patch no longer applied to 1.18.0's Cargo.lock (rustls-webpki 0.103.13, webpki-root-certs 1.0.7, aws-lc-rs 1.17.0). Replaced with `pkgmgr lock-patch nickel-lsp --replace-legacy --advisory-source osv`, run in the deployed runner image (pkgmgr 0b705d3-sc2e851aa, cargo 1.98.1) via Cloud Build 79c2d555. Base lock sha256 2fdafec3...3ec2. Floors met: rustls-webpki 0.103.16, webpki-root-certs 1.0.10 (CVE-2026-111943), plus anyhow, crossbeam-epoch, cxx, faster-hex, h2, memmap2, quinn-proto, rustls, tokio. Companions include aws-lc-rs 1.19.0 / aws-lc-sys 0.47.0. Unresolved, left to a human (header): bitmaps 3.2.1 (no fixed release), imbl-sized-chunks 0.1.3, quick-xml 0.26.0 / 0.38.3 (semver-incompatible fixes). The hand patch's apply line and exact-version check go; its CVE-2026-111943 floor check stays below the generated block. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Replaced the hand-written How it was produced: Floors met (from the patch header):
Companions (cargo moved these to satisfy the floors): aws-lc-rs 1.17.0 → 1.19.0, aws-lc-sys 0.41.0 → 0.47.0 (the Unresolved: left to a human, NOT fixed by this patch. These are pre-existing, and not part of CVE-2026-111943:
build.sh: the generated block (base-lock sha256 check, CI:
|
Update nickel-lsp
1.17.0→1.18.0Source:
github:nickel-lang/nickelRelease: https://github.com/nickel-lang/nickel/releases/tag/1.18.0
Changelog: nickel-lang/nickel@1.17.0...1.18.0
Released: 40 days ago (2026-09-19)
Caution
Security floor not met: rustls-webpki 0.103.13 < 0.103.16 (CVE-2026-111943 / RUSTSEC-2026-0382); webpki-root-certs 1.0.7 < 1.0.10 (CVE-2026-111943 / RUSTSEC-2026-0383) —
cve-2026-111943-webpki-lock.patchno longer applies to 1.18.0's ownCargo.lock, and that lock is still below the floor (data/security_floors.tomlin pkgmgr-rs). Regenerate the lock delta against 1.18.0 (cargo update -p <crate> --precise <fixed>, resolution only) and keep the build.sh guard; do NOT drop the patch.Warning
Carried patches will break this build — opened as a draft. Fix the recipe before merging.
cve-2026-111943-webpki-lock.patchneither applies nor reverse-applies to 1.18.0 (patch -p1 --dry-run): rebase it onto 1.18.0 or drop it.Forward dry-run:
Reverse dry-run:
Carried patches vs 1.18.0
Each
| Localpatch was dry-run against the extracted 1.18.0 tree, forward and reverse, both with exact context (patch -N -F0,patch -R -F0). Only a patch that reverse-applies WHOLE is treated as upstream; a partial match is a conflict, and one that applies forward only with fuzz is reported as such.cve-2026-111943-webpki-lock.patch— neither direction applies to 1.18.0 (see the warning above). Security floors 1.18.0's own lock misses: rustls-webpki 0.103.13 < 0.103.16 (CVE-2026-111943 / RUSTSEC-2026-0382); webpki-root-certs 1.0.7 < 1.0.10 (CVE-2026-111943 / RUSTSEC-2026-0383).Components changed
CycloneDX component delta (declared materials — the package's own version, not a dependency-tree diff)
nickel-lsp1.17.01.18.0nickel-lsp-upstream1.17.01.18.0Changes
1.17.01.18.08cc47b3a2b9ed4e3...ddcac13684c1fc17...https://github.com/nickel-lang/nickel/archive/refs/tags/1.17.0.tar.gzhttps://github.com/nickel-lang/nickel/archive/refs/tags/1.18.0.tar.gzMIT(source: GitHub + tarball)🔒 TLS:
github.com— Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (rootc90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519 ⇒codeload.github.com— Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (rootc90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519Quality suggestions
testsblock. This package has no standalone tests, so the buildbot will only verify compilation — not functional correctness. Consider adding a minimal smoke test (e.g., a--versionor small round-trip invocation) as part of this PR so future bumps catch regressions. Seepackages/python/build.nclfor a simple example.Created by pkgmgr