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

Commit a frontend lockfile to ensure reproducible builds #215

New Issue
Closed
opened 2026-03-27 05:24:00 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 05:24:00 +00:00
Owner
Copy Link
Copy Source

Context

The frontend has no package-lock.json or pnpm-lock.yaml committed to the repository. This means npm install / pnpm install can resolve different dependency versions on each run, causing non-reproducible builds.

Roadmap reference: ROADMAP.md > P2 > Frontend > Missing package-lock.json or pnpm-lock.yaml

What to do

  • From a clean state, run npm install (or pnpm install) to generate a lockfile.
  • Commit the generated package-lock.json (or pnpm-lock.yaml) to the repository.
  • Add a CI step that runs npm ci (or pnpm install --frozen-lockfile) to enforce the lockfile.
  • Remove package-lock.json or yarn.lock from .gitignore if it was listed there.

Acceptance criteria

  • A lockfile is present in the frontend/ directory and tracked by git.
  • CI uses npm ci or equivalent frozen-lockfile install.
  • npm ci completes without errors.
## Context The frontend has no `package-lock.json` or `pnpm-lock.yaml` committed to the repository. This means `npm install` / `pnpm install` can resolve different dependency versions on each run, causing non-reproducible builds. Roadmap reference: ROADMAP.md > P2 > Frontend > Missing package-lock.json or pnpm-lock.yaml ## What to do - From a clean state, run `npm install` (or `pnpm install`) to generate a lockfile. - Commit the generated `package-lock.json` (or `pnpm-lock.yaml`) to the repository. - Add a CI step that runs `npm ci` (or `pnpm install --frozen-lockfile`) to enforce the lockfile. - Remove `package-lock.json` or `yarn.lock` from `.gitignore` if it was listed there. ## Acceptance criteria - A lockfile is present in the `frontend/` directory and tracked by git. - CI uses `npm ci` or equivalent frozen-lockfile install. - `npm ci` completes without errors.
AI-Manager added the P2agent-readysmall labels 2026-03-27 05:24:00 +00:00
AI-Manager commented 2026-03-27 06:05:07 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the current codebase.

frontend/package-lock.json is committed to the repository. The CI workflow uses npm ci which relies on this lockfile for reproducible builds.

Closing as already implemented.

This issue has already been resolved in the current codebase. `frontend/package-lock.json` is committed to the repository. The CI workflow uses `npm ci` which relies on this lockfile for reproducible builds. Closing as already implemented.
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 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#215
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?