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

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

New Issue
Closed
opened 2026-03-30 19:23:53 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 19:23:53 +00:00
Owner
Copy Link
Copy Source

Summary

The frontend repository has no committed lockfile. This means npm install or pnpm install can resolve different dependency versions on different machines or in CI.

What to do

  • Run npm install (or pnpm install) in the frontend directory to generate a lockfile.
  • Commit package-lock.json or pnpm-lock.yaml.
  • Remove the lockfile pattern from .gitignore if it is currently excluded.
  • Verify CI uses npm ci (or equivalent) rather than npm install to enforce the lockfile.

Acceptance criteria

  • A lockfile is present and committed in the frontend directory.
  • npm ci succeeds in a clean environment.
  • CI build uses the lockfile.

References

Roadmap: P2 Frontend -- missing lockfile.

## Summary The frontend repository has no committed lockfile. This means `npm install` or `pnpm install` can resolve different dependency versions on different machines or in CI. ## What to do - Run `npm install` (or `pnpm install`) in the frontend directory to generate a lockfile. - Commit `package-lock.json` or `pnpm-lock.yaml`. - Remove the lockfile pattern from `.gitignore` if it is currently excluded. - Verify CI uses `npm ci` (or equivalent) rather than `npm install` to enforce the lockfile. ## Acceptance criteria - [ ] A lockfile is present and committed in the frontend directory. - [ ] `npm ci` succeeds in a clean environment. - [ ] CI build uses the lockfile. ## References Roadmap: P2 Frontend -- missing lockfile.
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-30 19:23:53 +00:00
AI-Manager commented 2026-03-30 20:04:06 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. frontend/package-lock.json is committed and tracked by git. The CI workflow uses npm ci which relies on the lockfile for reproducible builds.

Closing as completed.

Already implemented. `frontend/package-lock.json` is committed and tracked by git. The CI workflow uses `npm ci` which relies on the lockfile for reproducible builds. Closing as completed.
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 frontend 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#1434
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?