Fix CI: commit root package-lock.json, opt into Node.js 24, update README for workspace install#11
Merged
Conversation
Agent-Logs-Url: https://github.com/Chamudu/SwiftLogistics/sessions/3a15b942-1bc2-4f45-93dd-b1413bb0d798 Co-authored-by: Chamudu <59128532+Chamudu@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix CI issues by adding package-lock.json and updating Node.js version
Fix CI: commit root package-lock.json, opt into Node.js 24, update README for workspace install
Apr 13, 2026
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
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.
CI was broken on two fronts:
npm cifailing with "Dependencies lock file is not found" (nopackage-lock.jsonat repo root), and Node.js 20 deprecation warnings fromactions/checkout@v4/actions/setup-node@v4.Workflow (
ci.yml)FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: trueat the top-levelenvto opt into Node.js 24 for all actions ahead of the forced June 2026 migrationnpm ci→ lintclient-app→ buildclient-app→docker compose config -qLockfile
package-lock.json(lockfileVersion 3, npm v9+) at repo root covering all workspace packages — required by bothnpm ciandcache: "npm"in setup-nodeREADME
npm installloop with singlenpm installfrom root (npm workspaces)npm cifor reproducible installs and the lockfile commitment requirementOriginal prompt
Resolve the following CI issues in Chamudu/SwiftLogistics:
CI fails with
Dependencies lock file is not foundbecause no lock file is present at repo root. GitHub Actions with npm expects a package-lock.json, npm-shrinkwrap.json, or yarn.lock for reproducible installs (especially with npm ci and caching on workspaces).There's also a deprecation warning: Node.js 20 actions are deprecated for checkout/setup-node. Actions will use Node.js 24 starting June 2026. The recommended fix is to opt in by setting the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable in the workflow.
Tasks:
Deliver as a PR targeting main branch.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: the thing is only back end interns are low, so i target se fullstack devops interns
Assistant: Then keep your CV “backend-strong” but market it as Full‑Stack + DevOps: you’ll get more matches while still looking technically deep.
What to adjust (so recruiters read you as full‑stack + DevOps)
Below is a remade version optimized for SE / Full‑Stack / DevOps internships, aligned with your repos (no overclaims).