leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Commit a frontend lockfile to ensure reproducible builds #1413

New Issue
Closed
opened 2026-03-30 18:23:37 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 18:23:37 +00:00
Owner
Copy Link
Copy Source

Context

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

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

What to do

  • Determine the package manager in use (npm or pnpm) by checking package.json for a packageManager field or the presence of a pnpm-workspace.yaml.
  • Run npm install or pnpm install locally to generate the lockfile.
  • Commit the lockfile (package-lock.json or pnpm-lock.yaml) and ensure it is not in .gitignore.
  • Update the Gitea Actions workflow to use npm ci (or pnpm install --frozen-lockfile) instead of npm install.

Acceptance criteria

  • A lockfile is present and committed in the frontend directory.
  • CI installs dependencies using the frozen lockfile command.
  • The frontend builds successfully in CI after the change.
## Context Roadmap item: P2 -- Frontend -- Missing package-lock.json or pnpm-lock.yaml The frontend directory has no committed lockfile. This means `npm install` or `pnpm install` can resolve different dependency versions on different machines or in CI, leading to non-reproducible builds and hard-to-debug issues. ## What to do - Determine the package manager in use (npm or pnpm) by checking `package.json` for a `packageManager` field or the presence of a `pnpm-workspace.yaml`. - Run `npm install` or `pnpm install` locally to generate the lockfile. - Commit the lockfile (`package-lock.json` or `pnpm-lock.yaml`) and ensure it is not in `.gitignore`. - Update the Gitea Actions workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) instead of `npm install`. ## Acceptance criteria - [ ] A lockfile is present and committed in the frontend directory. - [ ] CI installs dependencies using the frozen lockfile command. - [ ] The frontend builds successfully in CI after the change.
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-30 18:23:37 +00:00
AI-Manager commented 2026-03-30 19:05:32 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already resolved in main.

frontend/package-lock.json is committed to the repository and CI uses npm ci (which requires it) in both .gitea/workflows/test.yaml and build.yaml. Closing as complete.

**Triage: Already resolved in main.** `frontend/package-lock.json` is committed to the repository and CI uses `npm ci` (which requires it) in both `.gitea/workflows/test.yaml` and `build.yaml`. 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 frontend 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#1413
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?