fix: pin rollup binary to 4.62.2 and restore lockfile to fix GoCD GLIBC failure - #79
Merged
Merged
Conversation
…BC failure @rollup/rollup-linux-x64-gnu@4.62.3 introduced a GLIBC_2.32 requirement that breaks nuxt prepare on GoCD's Linux agents (GLIBC_2.31). Pin both rollup linux binaries to exactly 4.62.2 (GLIBC_2.14 only) and commit the lockfile so npm install on CI reads from it directly — no peer dep resolution, no arborist crash, no GLIBC mismatch.
netrajpatel
approved these changes
Jul 30, 2026
maheshmotkar-cs
approved these changes
Jul 30, 2026
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
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
3 participants
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.
Problem
GoCD CI was failing during
nuxt preparewith:Two compounding issues:
package-lock.jsonwas deleted — without it,npm installon CI resolves^4.62.2to the latest matching version (4.62.3), which introduced aGLIBC_2.32requirement@rollup/rollup-linux-x64-gnu@4.62.3cannot load,nuxt preparefailsFix
@rollup/rollup-linux-x64-gnuand@rollup/rollup-linux-x64-muslto exact4.62.2(requiresGLIBC_2.14only — confirmed by binary inspection)package-lock.jsonwith4.62.2locked — GoCD reads from it directly, no resolution step, no chance of picking up a newer breaking versionTest plan
nuxt preparenpm installcompletes without errorsnpm run buildsucceedsnpm run devstarts without issues