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 #937

New Issue
Closed
opened 2026-03-29 08:25:02 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 08:25:02 +00:00
Owner
Copy Link
Copy Source

Summary

The frontend has no lockfile committed. Without a lockfile, installs resolve to the latest compatible versions at build time, producing non-reproducible builds and making dependency auditing difficult.

Roadmap Reference

P2 Frontend -- Missing package-lock.json or pnpm-lock.yaml (ROADMAP.md)

What to do

  1. Choose a package manager (npm or pnpm) consistent with existing scripts.
  2. Run install in the frontend directory to generate the lockfile.
  3. Commit the lockfile to the repository.
  4. Ensure .gitignore does NOT exclude the lockfile.
  5. Update CI to use frozen installs (npm ci or pnpm install --frozen-lockfile).

Acceptance criteria

  • A lockfile is present and committed.
  • CI installs dependencies using the lockfile and fails if it is out of date.
  • The frontend builds successfully in CI after this change.
## Summary The frontend has no lockfile committed. Without a lockfile, installs resolve to the latest compatible versions at build time, producing non-reproducible builds and making dependency auditing difficult. ## Roadmap Reference P2 Frontend -- Missing package-lock.json or pnpm-lock.yaml (ROADMAP.md) ## What to do 1. Choose a package manager (npm or pnpm) consistent with existing scripts. 2. Run install in the frontend directory to generate the lockfile. 3. Commit the lockfile to the repository. 4. Ensure .gitignore does NOT exclude the lockfile. 5. Update CI to use frozen installs (npm ci or pnpm install --frozen-lockfile). ## Acceptance criteria - A lockfile is present and committed. - CI installs dependencies using the lockfile and fails if it is out of date. - The frontend builds successfully in CI after this change.
AI-Manager added the P2agent-readysmallfeature labels 2026-03-29 08:25:02 +00:00
AI-Manager commented 2026-03-29 09:02:42 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. frontend/package-lock.json is tracked in git (committed in PR #31). The CI uses npm ci which depends on this lockfile for reproducible builds. Closing as completed.

This issue has been resolved. `frontend/package-lock.json` is tracked in git (committed in PR #31). The CI uses `npm ci` which depends on this 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 feature 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#937
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?