davsclaus opened a new pull request, #1747: URL: https://github.com/apache/camel-website/pull/1747
Fixes the `main` CI failure since #1740 (https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/2786/). ### Root cause #1740 changed one line in the `github-release-binary.js` yarn plugin: the `exec.js` stub it writes into the faux cargo-deadlinks package swapped `rmdirSync` for `rmSync`. The stub is part of the package archive, so the archive bytes and the lockfile checksum for the Linux deadlinks binary changed. Yarn 4 names global-cache files by locator hash only (`@deadlinks-cargo-deadlinks-github-release-a675f573c0-10.zip`), not by checksum. CI keeps its yarn cache across builds, so `yarn install` found the old archive under the same name and failed with YN0018 "The remote archive doesn't match the expected checksum" instead of refetching. The same happens on any developer machine that installed before #1740. The Jenkinsfile chains `yarn install && ... ; yarn build-all`, so the build still ran, against stale `node_modules` without the new font packages, and the antora-ui-camel gulp build died with "Did you forget to signal async completion?". That was only a symptom. ### Fix - `github-release-binary.js`: revert the stub line to `rmdirSync`, so a fresh fetch is byte-identical to the archive CI already has cached. - `yarn.lock`: the three deadlinks checksums recomputed with the reverted template. Linux returns to its pre-#1740 value; the new macOS and Windows entries get their matching values. ### Verified - The freshly built Linux archive is byte-identical to a pre-#1740 cache copy. - Fresh-cache `yarn install --immutable` on Linux (node:lts in Docker) passes. - `yarn install --immutable` on macOS passes and `yarn build` in antora-ui-camel completes through `bundle:pack`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Ue7BFcXRDGZvRpovC3EtSR -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
