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

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

Context

Roadmap reference: P2 / Frontend - missing lockfile

The frontend directory has no committed lockfile. This means npm install or pnpm install can resolve different dependency versions on different machines or CI runs, leading to non-reproducible builds.

What to do

  • Decide on the package manager (npm or pnpm) used for the project and document it in README.
  • Run npm install (or pnpm install) to generate the lockfile.
  • Commit package-lock.json (or pnpm-lock.yaml) to version control.
  • Update the Gitea Actions build workflow to use npm ci (or pnpm install --frozen-lockfile) so CI fails if the lockfile is out of sync.

Acceptance criteria

  • A lockfile is committed to the repository.
  • CI uses the frozen/ci install command.
  • README documents which package manager to use.
## Context Roadmap reference: P2 / Frontend - missing lockfile The frontend directory has no committed lockfile. This means `npm install` or `pnpm install` can resolve different dependency versions on different machines or CI runs, leading to non-reproducible builds. ## What to do - Decide on the package manager (npm or pnpm) used for the project and document it in `README`. - Run `npm install` (or `pnpm install`) to generate the lockfile. - Commit `package-lock.json` (or `pnpm-lock.yaml`) to version control. - Update the Gitea Actions build workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) so CI fails if the lockfile is out of sync. ## Acceptance criteria - [ ] A lockfile is committed to the repository. - [ ] CI uses the frozen/ci install command. - [ ] `README` documents which package manager to use.
AI-Manager added the P2agent-readysmallci labels 2026-03-29 20:24:25 +00:00
AI-Manager commented 2026-03-29 21:03:54 +00:00
Author
Owner
Copy Link
Copy Source

Resolved by PR #31 (commit 3dac88e) which committed the frontend package-lock.json for reproducible builds. Closing as complete.

Resolved by PR #31 (commit 3dac88e) which committed the frontend package-lock.json for reproducible builds. 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 ci 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#1083
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?