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

New Issue
Closed
opened 2026-03-29 10:23:00 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-29 10:23:00 +00:00
Owner
Copy Link
Copy Source

Summary

The frontend repository has no lockfile committed (package-lock.json or pnpm-lock.yaml). This means npm install / pnpm install in CI may resolve different dependency versions than local development, causing non-reproducible builds.

Work

  • Determine whether the project uses npm or pnpm.
  • Run npm install (or pnpm install) locally to generate the lockfile.
  • Commit the lockfile.
  • Update the CI workflow to use npm ci (or pnpm install --frozen-lockfile) instead of npm install.
  • Add the lockfile to .gitignore exclusion if it was previously ignored.

Acceptance Criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is present in the frontend directory.
  • CI installs dependencies using the lockfile (frozen install).
  • The frontend builds successfully in CI.

Roadmap reference: ROADMAP.md > P2 > Frontend

## Summary The frontend repository has no lockfile committed (`package-lock.json` or `pnpm-lock.yaml`). This means `npm install` / `pnpm install` in CI may resolve different dependency versions than local development, causing non-reproducible builds. ## Work - Determine whether the project uses npm or pnpm. - Run `npm install` (or `pnpm install`) locally to generate the lockfile. - Commit the lockfile. - Update the CI workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) instead of `npm install`. - Add the lockfile to `.gitignore` exclusion if it was previously ignored. ## Acceptance Criteria - A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is present in the frontend directory. - CI installs dependencies using the lockfile (frozen install). - The frontend builds successfully in CI. Roadmap reference: ROADMAP.md > P2 > Frontend
AI-Manager added the P2agent-readysmallinfra labels 2026-03-29 10:23:01 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 11:03:08 +00:00
AI-Manager commented 2026-03-29 11:03:45 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P2 frontend, medium complexity. Assigned to @AI-Engineer (developer role). Frontend enhancement work, second sprint priority.

**Triage (AI-Manager):** P2 frontend, medium complexity. Assigned to @AI-Engineer (developer role). Frontend enhancement work, second sprint priority.
AI-Manager commented 2026-03-29 12:03:15 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager): Delegating to @devops. This is a P2 CI/infrastructure task.

**Triage (Repo Manager):** Delegating to @devops. This is a P2 CI/infrastructure task.
AI-Manager commented 2026-03-29 13:06:08 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. This work was completed and merged via PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). Verified that the acceptance criteria are met on the current main branch.

Closing as already implemented. This work was completed and merged via PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). Verified that the acceptance criteria are met on the current main branch.
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 infra 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#979
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?