docs: Update outdated GitHub Actions versions#11774
docs: Update outdated GitHub Actions versions#11774pgoslatara wants to merge 5 commits intoSignificant-Gravitas:devfrom
Conversation
github-project-automation
bot
moved this to 🆕 Needs initial review
in AutoGPT development kanban
|
|
WalkthroughGitHub Actions workflow files across the repository are updated with newer major/minor versions of standard GitHub Actions tools. All 23 workflow files receive version bumps for checkout, setup-python, setup-node, cache, upload-artifact, github-script, and related actions. No functional logic or control flow modifications are introduced. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This PR targets the Automatically setting the base branch to |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #11774 +/- ##
======================================
Coverage ? 49.61%
======================================
Files ? 144
Lines ? 8914
Branches ? 1240
======================================
Hits ? 4423
Misses ? 4344
Partials ? 147
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ⓘ Your approaching your monthly quota for Qodo. Upgrade your plan PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/platform-frontend-ci.yml (1)
240-256: Inconsistentupload-artifactversions.Line 242 uses
actions/upload-artifact@v6while Line 251 still usesactions/upload-artifact@v4. This appears to be an oversight - both artifact upload steps should use the same version for consistency.Proposed fix
- name: Upload Playwright test results if: always() - uses: actions/upload-artifact@v4 + uses: actions/upload-artifact@v6 with: name: playwright-test-results path: test-results if-no-files-found: ignore retention-days: 3
🤖 Fix all issues with AI agents
In @.github/workflows/platform-frontend-ci.yml:
- Around line 33-36: Update the workflow to account for breaking changes in
actions/checkout@v6 and actions/setup-node@v6: verify and, if needed, pin or
roll back the uses entries for actions/checkout@v6 and actions/setup-node@v6;
ensure any logic that depended on the old persist-credentials behavior is
updated (or set persist-credentials explicitly / upgrade Actions Runner to
v2.329.0+ if you need authenticated git inside Docker); remove any use of the
removed always-auth input for setup-node and adjust npm caching behavior by
setting packageManager or devEngines in package.json or configuring setup-node
cache inputs to achieve the previous behavior.
🧹 Nitpick comments (1)
.github/workflows/classic-benchmark_publish_package.yml (1)
20-21: Consider updating Python version (out of scope for this PR).Python 3.8 reached end-of-life in October 2024. While this is unrelated to the GitHub Actions version updates in this PR, consider updating to a supported Python version (3.10+) in a future PR.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (22)
.github/workflows/classic-autogpt-ci.yml.github/workflows/classic-autogpt-docker-cache-clean.yml.github/workflows/classic-autogpt-docker-ci.yml.github/workflows/classic-autogpt-docker-release.yml.github/workflows/classic-autogpts-ci.yml.github/workflows/classic-benchmark-ci.yml.github/workflows/classic-benchmark_publish_package.yml.github/workflows/classic-forge-ci.yml.github/workflows/classic-frontend-ci.yml.github/workflows/classic-python-checks.yml.github/workflows/claude-ci-failure-auto-fix.yml.github/workflows/claude-dependabot.yml.github/workflows/claude.yml.github/workflows/codeql.yml.github/workflows/copilot-setup-steps.yml.github/workflows/platform-autogpt-deploy-dev.yaml.github/workflows/platform-autogpt-deploy-prod.yml.github/workflows/platform-backend-ci.yml.github/workflows/platform-dev-deploy-event-dispatcher.yml.github/workflows/platform-frontend-ci.yml.github/workflows/platform-fullstack-ci.yml.github/workflows/repo-workflow-checker.yml
🧰 Additional context used
🧠 Learnings (19)
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/frontend/**/*.{ts,tsx,json} : Use Node.js 21+ with pnpm package manager for frontend development
Applied to files:
.github/workflows/platform-frontend-ci.yml.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:49:03.583Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: autogpt_platform/CLAUDE.md:0-0
Timestamp: 2025-11-25T08:49:03.583Z
Learning: Applies to autogpt_platform/backend/** : Install dependencies for backend using `poetry install`
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/backend/**/*.py : Use Python 3.10-3.13 with Python 3.11 required for development (managed by Poetry via pyproject.toml)
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/backend/pyproject.toml : Use Poetry for Python dependency management. Always verify pyproject.toml lock validation in CI
Applied to files:
.github/workflows/claude.yml.github/workflows/classic-autogpt-ci.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/backend/**/*.py : Always run backend setup commands in order: poetry install, poetry run prisma migrate dev, poetry run prisma generate before backend development
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:49:03.583Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: autogpt_platform/CLAUDE.md:0-0
Timestamp: 2025-11-25T08:49:03.583Z
Learning: Applies to autogpt_platform/backend/**/*_test.py : Run backend tests using `poetry run test` or `poetry run pytest path/to/test_file.py::test_function_name`
Applied to files:
.github/workflows/claude.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/backend/blocks/test/**/*.py : For backend tests, use poetry run pytest for validation. Block tests: poetry run pytest backend/blocks/test/test_block.py -xvs. Specific block: poetry run pytest 'backend/blocks/test/test_block.py::test_available_blocks[BlockName]' -xvs. Use --snapshot-update when output changes and always review with git diff
Applied to files:
.github/workflows/claude.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/backend/**/*.py : Always run poetry run format (Black + isort) before poetry run lint (ruff) for backend code
Applied to files:
.github/workflows/claude.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:55.844Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-25T08:48:55.844Z
Learning: Applies to autogpt_platform/backend/**/*.test.py : Run `poetry run test` for backend testing using pytest with docker-based postgres + prisma
Applied to files:
.github/workflows/claude.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:55.844Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-25T08:48:55.844Z
Learning: Applies to autogpt_platform/{backend,autogpt_libs}/**/*.py : Format Python code with `poetry run format`
Applied to files:
.github/workflows/claude.yml
📚 Learning: 2025-11-25T08:49:03.583Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: autogpt_platform/CLAUDE.md:0-0
Timestamp: 2025-11-25T08:49:03.583Z
Learning: Applies to autogpt_platform/backend/** : Run database migrations using `poetry run prisma migrate dev`
Applied to files:
.github/workflows/claude.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/frontend/package.json : Use pnpm for Node.js package management in frontend. Verify pnpm lock validation
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:49:03.583Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: autogpt_platform/CLAUDE.md:0-0
Timestamp: 2025-11-25T08:49:03.583Z
Learning: Applies to autogpt_platform/frontend/** : Install frontend dependencies using `pnpm i` instead of npm
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/frontend/**/*.{ts,tsx} : Always run pnpm install before frontend development, then use pnpm dev to start development server on port 3000
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:55.844Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-25T08:48:55.844Z
Learning: Applies to autogpt_platform/frontend/**/*.{js,ts,jsx,tsx} : Format frontend code using `pnpm format`
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:55.844Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-25T08:48:55.844Z
Learning: Applies to autogpt_platform/frontend/**/*.{test,spec}.{ts,tsx} : Run `pnpm test` or `pnpm test-ui` for frontend Playwright tests before committing
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Applies to autogpt_platform/frontend/**/*.{ts,tsx} : For frontend code formatting and linting, always run pnpm format
Applied to files:
.github/workflows/claude.yml.github/workflows/copilot-setup-steps.yml.github/workflows/claude-dependabot.yml
📚 Learning: 2025-11-25T08:48:33.246Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-25T08:48:33.246Z
Learning: Ensure Docker services (database, redis, rabbitmq, clamav) are always running before starting backend development by running: cd autogpt_platform && docker compose --profile local up deps --build --detach
Applied to files:
.github/workflows/platform-fullstack-ci.yml
📚 Learning: 2025-11-25T08:49:03.583Z
Learnt from: CR
Repo: Significant-Gravitas/AutoGPT PR: 0
File: autogpt_platform/CLAUDE.md:0-0
Timestamp: 2025-11-25T08:49:03.583Z
Learning: Applies to autogpt_platform/backend/**/*.py : Run linting and formatting: use `poetry run format` (Black + isort) to auto-fix, and `poetry run lint` (ruff) to check remaining errors
Applied to files:
.github/workflows/claude-dependabot.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Seer Code Review
🔇 Additional comments (22)
.github/workflows/classic-autogpt-docker-cache-clean.yml (1)
19-19: Version update noted; verification pending from earlier comments.The checkout action upgrade is consistent with the other workflow files in this PR. Assuming the version verification passes (as flagged in earlier comments), this change looks good.
.github/workflows/classic-autogpt-docker-ci.yml (2)
38-38: LGTM for the build job checkout update.Consistent with the PR-wide version upgrade pattern.
103-106: LGTM for the test job checkout update.The
submodules: trueoption should remain compatible with the upgraded checkout action version..github/workflows/platform-autogpt-deploy-prod.yml (1)
19-27: Production workflow - ensure version compatibility is validated before merge.This workflow deploys to the production environment. Given the criticality, ensure that:
- The upgraded action versions (
checkout@v6,setup-python@v6) are verified to exist- The workflow is tested in a non-production environment first
- The
refparameter behavior remains consistent with the new checkout version.github/workflows/codeql.yml (1)
61-61: No action needed.actions/checkout@v6is stable and released (v6.0.1 from Dec 2, 2025)..github/workflows/repo-workflow-checker.yml (1)
14-20: No action needed. Bothactions/checkout@v6(v6.0.2, released Jan 9, 2026) andactions/setup-python@v6(v6.1.0, released Nov 25, 2025) are current, stable versions and are compatible with the workflow configuration..github/workflows/classic-autogpts-ci.yml (1)
47-55: Action version updates are valid.The
actions/setup-python@v6exists and supports Python 3.13 and other versions. "Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release."Since this workflow uses
ubuntu-latest, the runner version requirement should be satisfied on GitHub-hosted runners..github/workflows/claude-ci-failure-auto-fix.yml (1)
25-29: Action version updates are valid.The
actions/checkout@v6upgrade is compatible with this workflow. "This is not a breaking change for most workflows, despite the major version bump, and... any bare git commands in my workflows will, in fact, continue to work without any changes."The workflow properly sets up git identity (lines 32-34) after checkout, which will work correctly with v6's credential handling.
Also applies to: 45-45
.github/workflows/platform-dev-deploy-event-dispatcher.yml (1)
20-20: GitHub Script action v8 upgrade is compatible with all scripts.All 7 instances updated from
actions/github-script@v7tov8. The scripts use standard Octokit API methods (github.rest.issues.createComment,github.rest.pulls.get,github.rest.issues.listComments) and modern JavaScript (const,await,forEach) that are fully compatible with v8's Node.js 24 runtime. Verify that your GitHub Actions runners meet the minimum version requirement (v2.327.1) for this action..github/workflows/classic-frontend-ci.yml (1)
28-28: Action version upgrades are compatible and verified.
actions/checkout@v6(v6.0.2 latest) andpeter-evans/create-pull-request@v8(v8.0.0 released Dec 9, 2025) are both valid. The create-pull-request v8 breaking changes (Actions Runner v2.327.1+ requirement for self-hosted runners) do not affect this workflow. The action's own documentation recommends actions/checkout@v6, making these upgrades aligned with upstream best practices..github/workflows/platform-fullstack-ci.yml (1)
32-37: Action versions are valid; verify runner compatibility for cache v5.The
actions/setup-node@v6(v6.1.0, latest) correctly removes always-auth configuration handling and upgrades@actions/cacheto 4.1.0. Theactions/cache@v5exists and is compatible with this workflow.Note that
actions/cache@v5requires GitHub Actions runner version 2.327.1 or newer. If your repository uses self-hosted runners, ensure they are updated before using this version, as they must meet the minimum requirement.Also applies to: 47-53, 66-73, 91-96
.github/workflows/classic-benchmark-ci.yml (1)
44-61: Version updates look consistent.The action version bumps (
checkout@v6,setup-python@v6,cache@v5) are applied consistently across both jobs in this workflow. The changes align with the PR's objective of updating GitHub Actions versions..github/workflows/platform-autogpt-deploy-dev.yaml (1)
27-35: LGTM!The action version updates are consistent and the workflow logic remains unchanged.
.github/workflows/classic-python-checks.yml (1)
35-36: LGTM!Version updates are applied consistently across all three jobs (
get-changed-parts,lint,types)..github/workflows/classic-autogpt-docker-release.yml (1)
22-23: LGTM!The checkout action version bump is consistent with the PR's update pattern.
.github/workflows/platform-backend-ci.yml (1)
71-71: Version updates verified and approved.The
actions/checkout@v6(latest version v6.0.1 as of December 2, 2025), actions/setup-python@v6, and actions/cache@v5 (which runs on Node.js 24 and requires a minimum Actions Runner version of 2.327.1) are all valid versions. Since this workflow runs on GitHub-hosted runners (ubuntu-latest), the runner version requirements will be automatically satisfied.Also applies to: 77-77, 91-91
.github/workflows/classic-forge-ci.yml (1)
66-66: Version updates verified and approved for multi-platform workflow.All updated action versions are valid:
actions/checkout@v6(v6.0.1), actions/setup-python@v6 (includes security fixes and upgraded dependencies), actions/cache@v5 (runs on Node.js 24, requires Actions Runner v2.327.1+), and actions/upload-artifact@v6 (runs on Node.js 24, requires Actions Runner v2.327.1+).Since the workflow uses GitHub-hosted runners (
ubuntu-latest,macos-latest,macos-14,windows-latest), the runner version requirements will be automatically met.Also applies to: 103-103, 110-110, 240-240
.github/workflows/classic-benchmark_publish_package.yml (1)
13-13: Version updates verified and approved.The
actions/checkout@v6andactions/setup-python@v6updates are valid and appropriate for this publish workflow.Also applies to: 19-19
.github/workflows/claude-dependabot.yml (1)
33-33: Version updates verified and approved.All updated action versions are valid:
actions/checkout@v6(v6.0.1)actions/setup-python@v6(requires runner v2.327.1+)actions/cache@v5(runs on Node.js 24, requires runner v2.327.1+)actions/setup-node@v6(includes changes to default auto-caching behavior for npm)Since this workflow runs on GitHub-hosted runners (
ubuntu-latest), all runner version requirements will be met.Also applies to: 39-39, 44-44, 81-81, 94-94, 127-127
.github/workflows/copilot-setup-steps.yml (1)
30-30: Version updates verified and approved.All updated action versions are valid and consistent with the broader PR pattern of upgrading to the latest stable versions. The workflow runs on GitHub-hosted runners (
ubuntu-latest), which will satisfy all runner version requirements.
actions/checkout@v6changes how credentials are persisted (storing under$RUNNER_TEMPinstead of directly in local git config), but this "is not a breaking change for most workflows" and "git push workflows will still work."Also applies to: 37-37, 42-42, 79-79, 92-92, 135-135
.github/workflows/claude.yml (1)
43-43: LGTM! GitHub Actions version updates are valid.The
actions/checkoutis now at v6.0.1, actions/setup-python v6.0.0, actions/setup-node v6.0.0, and actions/cache v5 which runs on Node.js 24. All updated versions exist and are the current stable releases.Runner compatibility note: actions/cache@v5 requires a minimum Actions Runner version of 2.327.1. actions/checkout@v6 requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios. GitHub-hosted runners (
ubuntu-latest) should already meet these requirements, but verify self-hosted runner versions if applicable.Also applies to: 55-55, 60-60, 97-97, 110-110, 143-143
.github/workflows/classic-autogpt-ci.yml (1)
64-64: LGTM! All action version updates are valid.actions/upload-artifact@v6 now runs on Node.js 24 and requires a minimum Actions Runner version of 2.327.1. Combined with the checkout, setup-python, and cache updates, all versions are consistent with the latest stable releases.
The cross-platform matrix (ubuntu, macos, macos-arm64, windows) should work correctly with these updated action versions on GitHub-hosted runners.
Also applies to: 75-75, 86-86, 142-142
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
| uses: actions/checkout@v6 | ||
|
|
||
| - name: Set up Node.js | ||
| uses: actions/setup-node@v4 | ||
| uses: actions/setup-node@v6 |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
actions/checkout v6 GitHub Actions release
💡 Result:
Short summary — actions/checkout v6 (GitHub):
- Latest v6 tag: v6.0.2 (released Jan 9, 2026). [1]
- Major changes in v6:
- persist-credentials now stores credentials in a separate file under $RUNNER_TEMP (improved credential security). [1][2]
- No workflow changes required for ordinary git operations (git fetch, git push continue to work). [2]
- Running authenticated git commands from a Docker container action requires Actions Runner v2.329.0 or later. [2][3]
Use: - uses: actions/checkout@v6. [2]
Sources:
- actions/checkout releases page (v6.0.2, v6.0.1, v6.0.0). [1]
- actions/checkout README / changelog (v6 what's new & usage). [2]
- GitHub Marketplace listing for Checkout (notes about runner requirement). [3]
🌐 Web query:
actions/setup-node v6 GitHub Actions release
💡 Result:
actions/setup-node v6 was released (see releases) — main points:
- v6.0.0 (release notes): breaking changes — automatic npm caching behavior changed (automatic npm cache enabled when package.json has packageManager/devEngines set to npm) and the deprecated always-auth input was removed. [1]
- v6.1.0: follow-up patch with dependency updates and removal of always-auth handling. [1]
- The repo README documents the v6 breaking changes and new caching defaults and usage examples (use package-manager-cache to opt out). [2]
Sources:
[1] actions/setup-node releases.
[2] actions/setup-node README / usage notes.
Review actions/checkout@v6 and actions/setup-node@v6 for breaking changes before merging.
Both versions exist (checkout v6.0.2, setup-node v6.0.0+) and include breaking changes:
- actions/checkout@v6: persist-credentials now stores credentials in a separate file. Running authenticated git commands from Docker container actions requires Actions Runner v2.329.0 or later.
- actions/setup-node@v6: Automatic npm caching behavior changed (now enabled when
packageManagerordevEnginesis set to npm in package.json); the deprecatedalways-authinput was removed.
Verify your CI/CD workflows don't rely on the removed always-auth input and confirm Actions Runner version meets the Docker container requirement if applicable.
🤖 Prompt for AI Agents
In @.github/workflows/platform-frontend-ci.yml around lines 33 - 36, Update the
workflow to account for breaking changes in actions/checkout@v6 and
actions/setup-node@v6: verify and, if needed, pin or roll back the uses entries
for actions/checkout@v6 and actions/setup-node@v6; ensure any logic that
depended on the old persist-credentials behavior is updated (or set
persist-credentials explicitly / upgrade Actions Runner to v2.329.0+ if you need
authenticated git inside Docker); remove any use of the removed always-auth
input for setup-node and adjust npm caching behavior by setting packageManager
or devEngines in package.json or configuring setup-node cache inputs to achieve
the previous behavior.
|
Hi there, thanks for making this pull request! I'm not sure why but the frontend CI seems very unhappy with these changes. Please make sure the "AutoGPT Platform - Frontend CI" passes, otherwise we can't merge this. Also, while you are right the listed action usages have newer major versions available, that doesn't make them deprecated. I've checked some of them and the versions we currently use are still fairly recent, most of them only a few months old. |
|
@Pwuts Can you re-run the "AutoGPT Platform - Frontend CI" test? I didn't change anything that should impact the test so I'm puzzled as to why it failed and wonder if it was a one-off. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| - name: Upload Playwright report | ||
| if: always() | ||
| uses: actions/upload-artifact@v4 | ||
| uses: actions/upload-artifact@v6 |
There was a problem hiding this comment.
Inconsistent upload-artifact version update in same workflow
Medium Severity
The PR updates one actions/upload-artifact usage to v6 at line 242 ("Upload Playwright report") but misses updating the second usage at line 251 ("Upload Playwright test results"), which remains at v4. This creates an inconsistent state where the same workflow file uses two different major versions of the same action. Since artifact actions v4 and v6 may have different behaviors or APIs, this could lead to subtle inconsistencies between the two artifact upload steps.
Additional Locations (1)
|
Hey mate -- this seems ai generated and thus not a high bar to close and if not -- theres a lot more work to be done. lmk how you want to handle that but closing for now |
github-project-automation
bot
moved this from 🆕 Needs initial review
to ✅ Done
in AutoGPT development kanban
4 participants
The PR updates outdated GitHub Action versions to ensure compatibility with the latest tools and features. Several workflows in the repository are using deprecated versions of actions like
actions/upload-artifact,actions/cache, andactions/checkout, which are now updated to versionv6orv8to support new functionality and improvements.Changes 🏗️
actions/upload-artifactfromv4tov6in.github/workflows/classic-forge-ci.ymlactions/setup-pythonfromv5tov6in.github/workflows/classic-benchmark_publish_package.ymlactions/checkoutfromv4tov6in.github/workflows/platform-fullstack-ci.ymlactions/cachefromv4tov5in.github/workflows/classic-benchmark-ci.ymlactions/github-scriptfromv7tov8in.github/workflows/platform-dev-deploy-event-dispatcher.ymlactions/checkoutfromv4tov6in.github/workflows/classic-python-checks.ymlactions/cachefromv4tov5in.github/workflows/platform-backend-ci.ymlactions/setup-pythonfromv5tov6in.github/workflows/platform-autogpt-deploy-dev.yamlactions/checkoutfromv4tov6in.github/workflows/claude.ymlactions/checkoutfromv4tov6in.github/workflows/classic-autogpt-ci.ymlactions/setup-nodefromv4tov6in.github/workflows/claude.ymlpeter-evans/create-pull-requestfromv7tov8in.github/workflows/classic-frontend-ci.ymlactions/github-scriptfromv7tov8in.github/workflows/claude-ci-failure-auto-fix.ymlactions/checkoutfromv4tov6in.github/workflows/codeql.ymlactions/checkoutfromv4tov6in.github/workflows/classic-autogpt-docker-cache-clean.ymlactions/setup-pythonfromv5tov6in.github/workflows/classic-forge-ci.ymlactions/checkoutfromv4tov6in.github/workflows/claude-dependabot.ymlactions/checkoutfromv4tov6in.github/workflows/classic-autogpts-ci.ymlactions/setup-nodefromv4tov6in.github/workflows/copilot-setup-steps.ymlactions/setup-pythonfromv5tov6in.github/workflows/classic-autogpt-ci.ymlactions/checkoutfromv4tov6in.github/workflows/classic-frontend-ci.ymlactions/checkoutfromv4tov6in.github/workflows/platform-autogpt-deploy-prod.ymlactions/setup-pythonfromv5tov6in.github/workflows/classic-benchmark-ci.ymlactions/setup-pythonfromv5tov6in.github/workflows/claude-dependabot.ymlactions/checkoutfromv4tov6in.github/workflows/classic-forge-ci.ymlactions/setup-nodefromv4tov6in.github/workflows/platform-fullstack-ci.ymlactions/cachefromv4tov5in.github/workflows/platform-fullstack-ci.ymlactions/checkoutfromv4tov6in.github/workflows/claude-ci-failure-auto-fix.ymlactions/upload-artifactfromv4tov6in.github/workflows/classic-autogpt-ci.ymlactions/checkoutfromv4tov6in.github/workflows/classic-autogpt-docker-ci.ymlactions/setup-nodefromv4tov6in.github/workflows/claude-dependabot.ymlactions/setup-pythonfromv5tov6in.github/workflows/claude.ymlactions/checkoutfromv4tov6in.github/workflows/repo-workflow-checker.ymlactions/cachefromv4tov5in.github/workflows/copilot-setup-steps.ymlactions/checkoutfromv4tov6in.github/workflows/copilot-setup-steps.ymlactions/checkoutfromv4tov6in.github/workflows/platform-backend-ci.ymlactions/checkoutfromv4tov6in.github/workflows/platform-frontend-ci.ymlactions/checkoutfromv4tov6in.github/workflows/classic-benchmark_publish_package.ymlactions/setup-pythonfromv5tov6in.github/workflows/copilot-setup-steps.ymlactions/setup-pythonfromv5tov6in.github/workflows/platform-autogpt-deploy-prod.ymlactions/checkoutfromv4tov6in.github/workflows/classic-autogpt-docker-release.ymlactions/cachefromv4tov5in.github/workflows/copilot-setup-steps.ymlactions/cachefromv4tov5in.github/workflows/classic-forge-ci.ymlactions/cachefromv4tov5in.github/workflows/platform-frontend-ci.ymlactions/cachefromv4tov5in.github/workflows/classic-python-checks.ymlactions/cachefromv4tov5in.github/workflows/claude-dependabot.ymlChecklist 📋
Test Plan
The changes will be tested in the CI pipeline of the pull request. The test plan includes:
claude.yml,platform-fullstack-ci.yml)Note
Repository-wide CI maintenance to keep workflows current and compatible.
actions/checkout@v6,actions/setup-python@v6,actions/setup-node@v6,actions/cache@v5,actions/upload-artifact@v6,actions/github-script@v8,peter-evans/create-pull-request@v8classic-autogpt-ci,classic-forge-ci,classic-autogpts-ci), Docker build/test/release, benchmarking, frontend CI, platform backend/frontend/fullstack CI, deploy pipelines, CodeQL, Copilot/Claude helpers, and repo status checkerWritten by Cursor Bugbot for commit c2b4931. This will update automatically on new commits. Configure here.