build(deps): bump rust from 1.95-alpine to 1.98-alpine in /relay - #313
build(deps): bump rust from 1.95-alpine to 1.98-alpine in /relay#313dependabot[bot] wants to merge 1 commit into
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
@dependabot rebase |
Bumps rust from 1.95-alpine to 1.98-alpine. --- updated-dependencies: - dependency-name: rust dependency-version: 1.98-alpine dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
3701b1d to
087936e
Compare
|
Niet mergen: dit is een echte incompatibiliteit, geen verouderde branch. De Dockerfile-build faalt na de rebase nog steeds, en nu om de juiste reden: rust 1.98-alpine breekt de liboqs-bindings. Wat er nodig is voordat deze bump kan: de oqs-crate en/of liboqs-versie mee-bumpen (of pinnen) zodat de struct-definities weer sporen met de code in relay/. Tot die tijd blijft 1.95-alpine de werkende toolchain. Vondst uit de nachtronde 2026-09-02; de vijf andere dependabot-PR's zijn na rebase en (voor de docker-publish-actions) een echte workflow_dispatch-validatie gemerged. |
|
Opgelost in #329 (neemt deze bump ongewijzigd over) samen met Apolloccrypt/paramant-core#24. Oorzaak was niet rustc maar libclang 22 in Alpine 3.24: bindgen 0.71 maakt de forward-declared OQS_SIG opaak. paramant-core bouwt oqs-sys nu met bindgen 0.72 (oqs 0.11.0). Deze PR kan dicht zodra #329 gemerged is. |
…-core with bindgen 0.72 (#329) * build(deps): bump rust from 1.95-alpine to 1.98-alpine in /relay Bumps rust from 1.95-alpine to 1.98-alpine. --- updated-dependencies: - dependency-name: rust dependency-version: 1.98-alpine dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> * Build the crypto binding on rust:1.98-alpine by adopting the paramant-core with bindgen 0.72 Dependabot's rust 1.95-alpine -> 1.98-alpine bump (#313) fails in the paramant-core-binding stage with E0609 "no field alg_version on type &OQS_SIG". The base image is not at fault: Alpine 3.24 ships libclang 22, under which bindgen 0.71 (pulled in by oqs-sys 0.11.0 and older) emits the forward-declared OQS_SIG as an opaque struct. Rustc version is irrelevant, paramant-core's rust-toolchain.toml pins 1.95.0 anyway. paramant-core#24 fixes that at the source (oqs 0.11.0, oqs-sys patched to the upstream commit with bindgen 0.72, musl CI job on this same rust:1.98-alpine digest), so this takes the base bump from #313 and moves both paramant-core pins, PARAMANT_CORE_COMMIT in the Dockerfile and PARAMANT_CORE_SHA in the crypto-suite job, to that commit. The Dockerfile comment that documented the 1.95 pin now documents the actual cause instead. Verified locally: `docker build` of relay/ with this Dockerfile completes (binding stage finishes `cargo build --locked --release`, final image builds); in the runtime image `require('@paramant/core')` loads the musl binding and ML-DSA-65 keygen/sign/verify round-trips; the relay crypto suite (144 tests) passes on the host against the binding built from paramant-core b90b3c5. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XJk2nCLCLmi3F71qkCUn7N --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
|
Looks like rust is up-to-date now, so this is no longer needed. |
#340 pinned one Node line across four places: `engines` (">=22 <25") in the root, relay and admin manifests, `.nvmrc`, the `node-version` steps in every CI job, and the base image in both Dockerfiles. Its own words: the range "makes adopting Node 26 a deliberate bump rather than an accident". Dependabot opened #343 and #346 (node 24-alpine3.24 -> 26-alpine3.24) within the hour. Node 26 is the next even line but does not reach Active LTS until late October 2026, and no `.npmrc` sets engine-strict, so `npm ci` inside the image never checks `engines`: both PRs went green while putting the image on a runtime all three manifests forbid. The docker updater for /relay and /admin now ignores semver-major on "node" only. The rust builder keeps its majors (#313 was a real break that had to be seen), and node minor/patch, Alpine rebuilds and digest updates still arrive weekly. Adopting a new LTS line stays a hand bump of the whole grid.
1 participant
Warning
Cooldown could not be applied because no publication date was available from the registry.
Bumps rust from 1.95-alpine to 1.98-alpine.