Skip to content

Fix various deprecations in GitHub workflows#4675

Merged
marcoacierno merged 5 commits into
mainfrom
update-actions
Jun 20, 2026
Merged

Fix various deprecations in GitHub workflows#4675
marcoacierno merged 5 commits into
mainfrom
update-actions

Conversation

@marcoacierno

@marcoacierno marcoacierno commented Jun 20, 2026

Copy link
Copy Markdown
Member

What

Update various actions to use the latest version and fix the NodeJS 20 warning

@vercel

vercel Bot commented Jun 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pycon Ready Ready Preview Jun 20, 2026 4:48pm

@marcoacierno marcoacierno changed the title update actions Fix various deprecations in GitHub workflows Jun 20, 2026
@codecov

codecov Bot commented Jun 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.52%. Comparing base (99de59b) to head (6004b86).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4675   +/-   ##
=======================================
  Coverage   92.52%   92.52%           
=======================================
  Files         359      359           
  Lines       10800    10800           
  Branches      821      821           
=======================================
  Hits         9993     9993           
  Misses        696      696           
  Partials      111      111           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@marcoacierno

Copy link
Copy Markdown
Member Author

@claude check why CI is failing and fix it

@claude

claude Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Claude finished @marcoacierno's task in 1m 33s —— View job


CI Failure Analysis Complete

  • Check CI logs to identify the failure
  • Analyze the root cause
  • Implement the fix (blocked - workflow file changes require workflows permission)

Root Cause: The pnpm/action-setup@v6 action has cache: true which defaults to looking for pnpm-lock.yaml in the repository root. However, this project's lock file is in frontend/pnpm-lock.yaml. The error message from CI:

Error: Some specified paths were not resolved, unable to cache dependencies.

Fix Required: In .github/workflows/frontend-lint.yml, change cache: true to cache: false in the pnpm/action-setup step. The actions/setup-node@v6 already handles caching with the correct path (frontend/pnpm-lock.yaml), so having caching enabled in both actions causes a conflict.

      - uses: pnpm/action-setup@v6
        name: Install pnpm
        with:
          version: 9
          run_install: false
-         cache: true
+         cache: false

I'm unable to push this change because GitHub App permissions don't allow modifying workflow files. Please apply this fix manually.


@marcoacierno

Copy link
Copy Markdown
Member Author

@claude check why CI is failing and fix it

@claude

claude Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Claude finished @marcoacierno's task in 2m 27s —— View job


CI Failure Fixed

  • Review previous CI failure analysis
  • Verify the root cause in the workflow file
  • Apply the fix
  • Push the changes

Root Cause: The frontend/pnpm-workspace.yaml file was missing the required packages field. When pnpm encounters a pnpm-workspace.yaml file without this field, it fails with:

ERROR  packages field missing or empty

Fix Applied: Added packages: ['.'] to frontend/pnpm-workspace.yaml to indicate the frontend directory itself is the package. This preserves the existing configuration options (allowBuilds, overrides, etc.) while satisfying pnpm's workspace requirements.

Commit: 719f619 - Add packages field to pnpm-workspace.yaml
| Branch: update-actions

pnpm requires the packages field when pnpm-workspace.yaml exists.
Without it, pnpm install fails with "packages field missing or empty".

Co-authored-by: Marco Acierno <marcoacierno@users.noreply.github.com>
@marcoacierno marcoacierno merged commit d050273 into main Jun 20, 2026
5 checks passed
@marcoacierno marcoacierno deleted the update-actions branch June 20, 2026 18:05
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