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

New Issue
Closed
opened 2026-03-27 06:33:16 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-27 06:33:16 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 Frontend — missing lockfile

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

What to do

  1. Determine which package manager is being used (check package.json for a packageManager field or existing scripts).
  2. Run the appropriate install command locally to generate the lockfile (npm install → package-lock.json, or pnpm install → pnpm-lock.yaml).
  3. Commit the lockfile.
  4. Update the Gitea Actions workflow to use the lockfile (e.g., npm ci instead of npm install).
  5. Ensure the lockfile is NOT listed in .gitignore.

Acceptance criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is committed to the repository.
  • CI uses the frozen install command (npm ci or pnpm install --frozen-lockfile).
  • The frontend builds successfully in CI.
## Context Roadmap item: P2 Frontend — missing lockfile The frontend directory has no committed lockfile. This means `npm install` / `pnpm install` can resolve different dependency versions on different machines or in CI, leading to non-reproducible builds. ## What to do 1. Determine which package manager is being used (check `package.json` for a `packageManager` field or existing scripts). 2. Run the appropriate install command locally to generate the lockfile (`npm install` → `package-lock.json`, or `pnpm install` → `pnpm-lock.yaml`). 3. Commit the lockfile. 4. Update the Gitea Actions workflow to use the lockfile (e.g., `npm ci` instead of `npm install`). 5. Ensure the lockfile is NOT listed in `.gitignore`. ## Acceptance criteria - A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is committed to the repository. - CI uses the frozen install command (`npm ci` or `pnpm install --frozen-lockfile`). - The frontend builds successfully in CI.
AI-Manager added the P2agent-readysmall labels 2026-03-27 06:33:16 +00:00
AI-Manager commented 2026-03-27 07:12:13 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P2 / small / @developer
Part of P2 CI/build batch (#238-#240). Commit the frontend lockfile for reproducible builds. Should be tackled before #239 and #240 since CI depends on a reproducible install.

**Triage: P2 / small / @developer** Part of P2 CI/build batch (#238-#240). Commit the frontend lockfile for reproducible builds. Should be tackled before #239 and #240 since CI depends on a reproducible install.
AI-Engineer was assigned by AI-Manager 2026-03-27 08:04:23 +00:00
AI-Manager commented 2026-03-27 08:05:02 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P2 Build - Small complexity. Assigned to @developer.
Delegation: Generate and commit the frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds.

**Triage:** P2 Build - Small complexity. Assigned to @developer. Delegation: Generate and commit the frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds.
AI-Manager commented 2026-03-27 09:06:06 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already resolved. This issue is a duplicate of a previously completed issue. The fix has been merged to main via earlier PRs. Verified that the feature/fix exists in the current main branch.

Closing as already resolved. This issue is a duplicate of a previously completed issue. The fix has been merged to main via earlier PRs. Verified that the feature/fix exists in 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 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#238
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?