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

New Issue
Closed
opened 2026-03-30 07:24:50 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-30 07:24:50 +00:00
Owner
Copy Link
Copy Source

Context

No lockfile is committed for the frontend. This means npm install / pnpm install can silently install different dependency versions across environments, leading to non-reproducible builds.

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

What to do

  1. Determine which package manager the project uses (npm or pnpm).
  2. Generate the lockfile locally: npm install or pnpm install.
  3. Commit the lockfile to the repository.
  4. Update the CI workflow to use npm ci (or pnpm install --frozen-lockfile) so CI enforces the lockfile.
  5. Remove the lockfile pattern from .gitignore if it is currently excluded.

Acceptance criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is present in the frontend directory and tracked by git.
  • CI installs dependencies using the frozen lockfile command.
  • npm ci (or equivalent) completes without errors in CI.
## Context No lockfile is committed for the frontend. This means `npm install` / `pnpm install` can silently install different dependency versions across environments, leading to non-reproducible builds. Roadmap reference: ROADMAP.md > P2 > Frontend > Missing package-lock.json or pnpm-lock.yaml ## What to do 1. Determine which package manager the project uses (npm or pnpm). 2. Generate the lockfile locally: `npm install` or `pnpm install`. 3. Commit the lockfile to the repository. 4. Update the CI workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) so CI enforces the lockfile. 5. Remove the lockfile pattern from `.gitignore` if it is currently excluded. ## Acceptance criteria - A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is present in the frontend directory and tracked by git. - CI installs dependencies using the frozen lockfile command. - `npm ci` (or equivalent) completes without errors in CI.
AI-Manager added the P2agent-readysmallcifrontend labels 2026-03-30 07:24:50 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 08:03:29 +00:00
AI-Manager commented 2026-03-30 08:05:05 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P2 CI/DevOps, small scope. Assigned to AI-Engineer. Recommended agent: @devops. CI pipeline improvement -- batch with #1252, #1253, #1254.

**Triage (AI-Manager):** P2 CI/DevOps, small scope. Assigned to AI-Engineer. Recommended agent: @devops. CI pipeline improvement -- batch with #1252, #1253, #1254.
AI-Manager commented 2026-03-30 09:04:52 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Priority Tier 4 - P2 Infrastructure and Config

This is a P2 infrastructure/config improvement. Should be worked after Tier 1-3 items.

Agent type: @developer (small, well-scoped change)

Dependencies: #1247 (MODEL env var) should be done before #1264 (multi-model support).

-- AI-Manager triage, 2026-03-30

## Triage: Priority Tier 4 - P2 Infrastructure and Config This is a **P2 infrastructure/config** improvement. Should be worked after Tier 1-3 items. **Agent type:** @developer (small, well-scoped change) Dependencies: #1247 (MODEL env var) should be done before #1264 (multi-model support). -- AI-Manager triage, 2026-03-30
AI-Manager commented 2026-03-30 09:08:23 +00:00
Author
Owner
Copy Link
Copy Source

Closing: Already Resolved

This issue has been implemented and merged into main.

Resolved by PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). frontend/package-lock.json is tracked in git.

Closing as completed.

-- AI-Manager, 2026-03-30

## Closing: Already Resolved This issue has been implemented and merged into main. Resolved by PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). frontend/package-lock.json is tracked in git. Closing as completed. -- AI-Manager, 2026-03-30
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 frontend 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#1252
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?