leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Commit frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #625

New Issue
Closed
opened 2026-03-28 11:22:56 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 11:22:56 +00:00
Owner
Copy Link
Copy Source

Context

The frontend directory has no lockfile committed. CI and developer installs resolve to whatever latest package versions exist at that moment, making builds non-reproducible and masking dependency version drift.

Roadmap item: P2 > Frontend > Missing lockfile

What to do

  • Determine which package manager the project uses (npm, pnpm, or yarn).
  • Run npm install / pnpm install to generate the lockfile.
  • Commit package-lock.json or pnpm-lock.yaml.
  • Update the CI workflow to run npm ci (or pnpm install --frozen-lockfile) instead of npm install so it fails if the lockfile is out of date.

Acceptance criteria

  • A lockfile is present and committed in the frontend directory.
  • CI uses the frozen-lockfile install command.
  • npm ci (or equivalent) passes cleanly.
## Context The frontend directory has no lockfile committed. CI and developer installs resolve to whatever latest package versions exist at that moment, making builds non-reproducible and masking dependency version drift. Roadmap item: P2 > Frontend > Missing lockfile ## What to do - Determine which package manager the project uses (npm, pnpm, or yarn). - Run `npm install` / `pnpm install` to generate the lockfile. - Commit `package-lock.json` or `pnpm-lock.yaml`. - Update the CI workflow to run `npm ci` (or `pnpm install --frozen-lockfile`) instead of `npm install` so it fails if the lockfile is out of date. ## Acceptance criteria - [ ] A lockfile is present and committed in the frontend directory. - [ ] CI uses the frozen-lockfile install command. - [ ] `npm ci` (or equivalent) passes cleanly.
AI-Manager added the P2agent-readysmallinfra labels 2026-03-28 11:22:56 +00:00
AI-Manager commented 2026-03-28 12:04:42 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. frontend/package-lock.json is committed to the repo.

Closing: already implemented on main. `frontend/package-lock.json` is committed to the repo.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready infra small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#625
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?