ci: install D toolchain from the pinned official tarball - #4
Merged
Conversation
The issue's condition -- wait for a setup-dlang revision built for Node 24 -- cannot be met: upstream's latest commit (d7d85fc, 2025-10-05) still declares the node20 runtime and their migration issue (#100) is open. Rather than keep the deprecation warning until upstream moves, drop the action entirely. The replacement downloads dmd.2.112.0.linux.tar.xz from downloads.dlang.org and verifies its SHA-256 before extracting, which pins the exact toolchain BYTES rather than a version string handed to a third-party action -- strictly stronger than the full-SHA action pin it replaces, and no JS runtime is involved at all. The dmd binary in that tarball is byte-identical (sha256 596c745f) to the locally verified v0.2.1 build environment's dmd 2.112.0; dub 1.41.0 ships in the same tarball. Dry-run receipt: the d lineage builds cli and unittest configs and passes its suite with ONLY the extracted tarball on PATH.
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.
Closes #3.
The issue's wait-for-upstream condition cannot be met:
dlang-community/setup-dlang's latest revision (d7d85fc, 2025-10-05) still declaresusing: "node20"in itsaction.yml, and upstream's Node migration issue (dlang-community/setup-dlang#100) is open with no Node 24 revision to pin to. So this drops the action instead of waiting.What replaces it
A plain
run:step that downloadsdmd.2.112.0.linux.tar.xzfromdownloads.dlang.org, verifies its SHA-256 (4556ecde...) before extracting, and putsdmd2/linux/bin64on the PATH withDC=dmd.compiler: dmd-2.112.0to whatever bytes the mirror served; this pins the toolchain bytes themselves.dmdbinary inside the pinned tarball is byte-identical (sha256596c745f...) to the locally verified v0.2.1 build environment's dmd 2.112.0.dub1.41.0 ships in the same tarball.Dry run
The
dlineage was built and tested locally with only the extracted tarball on PATH (env -iwith the tarball'sbin64prepended):dub build --config=cli,dub build --config=unittest, andbaionstd-canon-testall pass (exit 0).The
verify (d)job on this PR is the live proof.