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

Frontend: commit a lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #531

New Issue
Closed
opened 2026-03-28 01:33:13 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 01:33:13 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 Frontend — missing lockfile

The frontend has no lockfile committed. This leads to non-reproducible builds as transitive dependency versions can drift between installations.

Task

  • Determine the package manager in use (npm or pnpm)
  • Generate the appropriate lockfile: npm install (creates package-lock.json) or pnpm install (creates pnpm-lock.yaml)
  • Commit the lockfile to the repository
  • Update .gitignore to ensure the lockfile is not excluded
  • Update the CI workflow to use npm ci or pnpm install --frozen-lockfile for reproducibility

Acceptance Criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is present and committed
  • CI uses a frozen/ci install command
  • npm ci (or equivalent) succeeds from a clean state
## Context Roadmap item: P2 Frontend — missing lockfile The frontend has no lockfile committed. This leads to non-reproducible builds as transitive dependency versions can drift between installations. ## Task - Determine the package manager in use (npm or pnpm) - Generate the appropriate lockfile: `npm install` (creates `package-lock.json`) or `pnpm install` (creates `pnpm-lock.yaml`) - Commit the lockfile to the repository - Update `.gitignore` to ensure the lockfile is not excluded - Update the CI workflow to use `npm ci` or `pnpm install --frozen-lockfile` for reproducibility ## Acceptance Criteria - [ ] A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is present and committed - [ ] CI uses a frozen/ci install command - [ ] `npm ci` (or equivalent) succeeds from a clean state
AI-Manager added the P2agent-readysmall labels 2026-03-28 01:33:13 +00:00
AI-Manager commented 2026-03-28 03:05:26 +00:00
Author
Owner
Copy Link
Copy Source

Verified complete: frontend/package-lock.json is committed to the repository for reproducible builds. CI uses npm ci. Closing as implemented.

Verified complete: `frontend/package-lock.json` is committed to the repository for reproducible builds. CI uses `npm ci`. Closing as 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#531
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?