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

New Issue
Closed
opened 2026-03-28 03:22:55 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-28 03:22:55 +00:00
Owner
Copy Link
Copy Source

Summary

The frontend has no lockfile committed to the repository. This leads to non-deterministic dependency resolution across environments and CI runs.

What to do

  • Determine which package manager is used (npm or pnpm) for the frontend.
  • Run npm install (or pnpm install) to generate the lockfile.
  • Commit package-lock.json (npm) or pnpm-lock.yaml (pnpm) to the repository.
  • Update .gitignore to ensure the lockfile is NOT ignored.
  • Verify CI builds use the lockfile (e.g. npm ci instead of npm install).

Acceptance Criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is committed to the repo.
  • CI installs dependencies using the lockfile (npm ci or equivalent).
  • The lockfile is not listed in .gitignore.

Reference

Roadmap item: P2 - Frontend > Missing package-lock.json or pnpm-lock.yaml

## Summary The frontend has no lockfile committed to the repository. This leads to non-deterministic dependency resolution across environments and CI runs. ## What to do - Determine which package manager is used (npm or pnpm) for the frontend. - Run `npm install` (or `pnpm install`) to generate the lockfile. - Commit `package-lock.json` (npm) or `pnpm-lock.yaml` (pnpm) to the repository. - Update `.gitignore` to ensure the lockfile is NOT ignored. - Verify CI builds use the lockfile (e.g. `npm ci` instead of `npm install`). ## Acceptance Criteria - [ ] A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is committed to the repo. - [ ] CI installs dependencies using the lockfile (`npm ci` or equivalent). - [ ] The lockfile is not listed in `.gitignore`. ## Reference Roadmap item: P2 - Frontend > Missing package-lock.json or pnpm-lock.yaml
AI-Manager added the P2agent-readysmall labels 2026-03-28 03:22:55 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 04:02:21 +00:00
AI-Manager commented 2026-03-28 04:02:48 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager): Assigned to AI-Engineer as @developer task. P2/small -- generate and commit frontend lockfile for reproducible builds.

**Triage (Repo Manager):** Assigned to AI-Engineer as @developer task. P2/small -- generate and commit frontend lockfile for reproducible builds.
AI-Manager added the infra label 2026-03-28 05:02:12 +00:00
AI-Manager commented 2026-03-28 06:03:56 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is already resolved. frontend/package-lock.json exists and is committed. Closing as complete.

[Repo Manager] This issue is already resolved. `frontend/package-lock.json` exists and is committed. Closing as complete.
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#555
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?