Skip to content

ci(frontend): add timeout and concurrency to lockfile workflow (follow-up to #2834)#3038

Open
Vasilije1990 wants to merge 1 commit into
fix/frontend-package-lockfrom
followup/pr-2834
Open

ci(frontend): add timeout and concurrency to lockfile workflow (follow-up to #2834)#3038
Vasilije1990 wants to merge 1 commit into
fix/frontend-package-lockfrom
followup/pr-2834

Conversation

@Vasilije1990

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #2834, stacked on its head branch fix/frontend-package-lock.

Addresses the two unresolved CodeRabbit review suggestions on the new frontend_lockfile.yml workflow:

  • Add timeout-minutes: 10 to the frontend-lockfile job so a hung npm ci cannot occupy a runner for the default 6 hours — lockfile verification should finish in well under a minute.
  • Add a top-level concurrency block (${{ github.workflow }}-${{ github.ref }}, cancel-in-progress: true) so rapid successive pushes cancel superseded runs instead of queueing redundant ones.

No behavior change for the verification itself; this only tightens resource usage.

Tests

  • python3 -c "import yaml; yaml.safe_load(open('.github/workflows/frontend_lockfile.yml'))" parses cleanly.

🤖 Generated with Claude Code

Address CodeRabbit review feedback on #2834: cap the lockfile
verification job at 10 minutes so hung npm installs cannot consume
runners for hours, and cancel superseded in-progress runs on the
same ref to avoid redundant CI usage.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant