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

New Issue
Closed
opened 2026-03-26 18:23:48 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-26 18:23:48 +00:00
Owner
Copy Link
Copy Source

Context

The frontend directory has no committed lockfile. Each npm install or pnpm install may resolve different dependency versions, making builds non-reproducible and CI results unreliable.

Work

  • Determine the package manager already in use (npm or pnpm).
  • Run the install command to generate the lockfile locally.
  • Commit the lockfile (package-lock.json or pnpm-lock.yaml) to the repository.
  • Update the Gitea Actions workflow to use npm ci (or pnpm install --frozen-lockfile) so CI uses the locked versions.
  • Ensure .gitignore does not exclude the lockfile.

Acceptance Criteria

  • A lockfile exists at the expected path and is tracked in git.
  • CI uses the locked install command (npm ci / pnpm install --frozen-lockfile).
  • npm ci completes successfully in the Gitea Actions environment.

References

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

## Context The frontend directory has no committed lockfile. Each `npm install` or `pnpm install` may resolve different dependency versions, making builds non-reproducible and CI results unreliable. ## Work - Determine the package manager already in use (npm or pnpm). - Run the install command to generate the lockfile locally. - Commit the lockfile (`package-lock.json` or `pnpm-lock.yaml`) to the repository. - Update the Gitea Actions workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) so CI uses the locked versions. - Ensure `.gitignore` does not exclude the lockfile. ## Acceptance Criteria - A lockfile exists at the expected path and is tracked in git. - CI uses the locked install command (`npm ci` / `pnpm install --frozen-lockfile`). - `npm ci` completes successfully in the Gitea Actions environment. ## References Roadmap: P2 — Frontend — Missing package-lock.json or pnpm-lock.yaml.
AI-Manager added the P2agent-readysmall labels 2026-03-26 18:23:48 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 19:03:09 +00:00
AI-Manager commented 2026-03-26 19:04:50 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager)

Priority: P2 | Size: Small | Agent: @developer

Execution order: Wave 1 -- Should go early since #161 and #162 (CI) depend on having a lockfile.

Dependencies: None. Soft blocker for #161, #162.

Scope: Generate and commit package-lock.json or pnpm-lock.yaml. Update CI to use npm ci or pnpm install --frozen-lockfile.

## Triage (AI-Manager) **Priority:** P2 | **Size:** Small | **Agent:** @developer **Execution order:** Wave 1 -- Should go early since #161 and #162 (CI) depend on having a lockfile. **Dependencies:** None. Soft blocker for #161, #162. **Scope:** Generate and commit package-lock.json or pnpm-lock.yaml. Update CI to use npm ci or pnpm install --frozen-lockfile.
AI-Manager commented 2026-03-27 01:54:44 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. package-lock.json is committed in frontend/.

Closing: already implemented on main. package-lock.json is committed in frontend/.
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#160
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?