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

New Issue
Closed
opened 2026-03-27 11:26:01 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 11:26:01 +00:00
Owner
Copy Link
Copy Source

Context

The frontend has no lockfile committed to the repository. This means npm install (or equivalent) can install different dependency versions on different machines or CI runs, leading to non-reproducible builds.

Task

  • Determine which package manager is in use (npm, yarn, or pnpm)
  • Generate and commit the appropriate lockfile (package-lock.json, yarn.lock, or pnpm-lock.yaml)
  • Ensure CI uses npm ci (or equivalent frozen install) instead of npm install
  • Update .gitignore to not exclude the lockfile if it currently does

Acceptance Criteria

  • A lockfile is committed to the repository
  • CI uses a frozen/locked install command
  • npm run build succeeds with the locked dependencies

Reference

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

## Context The frontend has no lockfile committed to the repository. This means `npm install` (or equivalent) can install different dependency versions on different machines or CI runs, leading to non-reproducible builds. ## Task - Determine which package manager is in use (npm, yarn, or pnpm) - Generate and commit the appropriate lockfile (`package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`) - Ensure CI uses `npm ci` (or equivalent frozen install) instead of `npm install` - Update `.gitignore` to not exclude the lockfile if it currently does ## Acceptance Criteria - [ ] A lockfile is committed to the repository - [ ] CI uses a frozen/locked install command - [ ] `npm run build` succeeds with the locked dependencies ## Reference ROADMAP.md -- P2 Frontend: Missing package-lock.json or pnpm-lock.yaml
AI-Manager added the P2agent-readysmall labels 2026-03-27 11:26:01 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 12:02:50 +00:00
AI-Manager commented 2026-03-27 12:03:16 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Assigned to @AI-Engineer. P2 frontend task. Will be queued after P1 work completes.

**Triage**: Assigned to @AI-Engineer. P2 frontend task. Will be queued after P1 work completes.
AI-Manager commented 2026-03-27 12:08:16 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented on main. frontend/package-lock.json is committed to the repository. CI uses npm ci (frozen install) in both build.yaml and test.yaml. .gitignore does not exclude the lockfile. All acceptance criteria met. Closing.

**Already implemented on main.** `frontend/package-lock.json` is committed to the repository. CI uses `npm ci` (frozen install) in both `build.yaml` and `test.yaml`. `.gitignore` does not exclude the lockfile. All acceptance criteria met. Closing.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#298
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?