Skip to content

Conversation

@radoering
Copy link
Member

@radoering radoering commented Sep 12, 2025

Summary by Sourcery

Update GitHub Actions versions across workflows and composite actions to the latest stable releases

Enhancements:

  • Upgrade actions/checkout to v5.0.0 in all workflows
  • Bump actions/cache to v4.2.4
  • Update actions/setup-node to v5.0.0
  • Upgrade amondnet/vercel-action to v41.1.4
  • Bump actions/download-artifact to v5.0.0
  • Update pypa/gh-action-pypi-publish to v1.13.0
  • Upgrade actions/setup-python to v6.0.0 in composite actions
  • Bump actions/create-github-app-token to v2.1.1

@sourcery-ai
Copy link

sourcery-ai bot commented Sep 12, 2025

Reviewer's Guide

This PR systematically updates pinned GitHub Actions in workflow and composite action definitions by replacing older commit hashes with the latest stable versions for checkout, caching, setup, artifact handling, and deployment steps.

File-Level Changes

Change Details Files
Upgrade checkout action to v5.0.0
  • Replaced all actions/checkout pins from previous v4.2.2 commit to v5.0.0
.github/workflows/.tests-matrix.yaml
.github/workflows/docs.yaml
.github/workflows/release.yaml
.github/workflows/tests.yaml
Bump cache action to v4.2.4
  • Updated actions/cache pins from v4.2.3 to v4.2.4 in caching steps
.github/workflows/.tests-matrix.yaml
.github/actions/poetry-install/action.yaml
Update core setup actions
  • Bumped actions/setup-python from v5.6.0 to v6.0.0
  • Bumped actions/setup-node from v4.4.0 to v5.0.0
.github/actions/bootstrap-poetry/action.yaml
.github/workflows/docs.yaml
Refresh artifact and deployment actions
  • Upgraded actions/download-artifact from v4.3.0 to v5.0.0
  • Upgraded pypa/gh-action-pypi-publish from v1.12.4 to v1.13.0
  • Upgraded amondnet/vercel-action from v25.2.0 to v41.1.4
.github/workflows/release.yaml
.github/workflows/docs.yaml
Bump backport authentication action
  • Updated actions/create-github-app-token from v2.0.2 to v2.1.1
.github/workflows/backport.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!

Blocking issues:

  • This GitHub Actions workflow file uses pull_request_target and checks out code from the incoming pull request. When using pull_request_target, the Action runs in the context of the target repository, which includes access to all repository secrets. Normally, this is safe because the Action only runs code from the target repository, not the incoming PR. However, by checking out the incoming PR code, you're now using the incoming code for the rest of the action. You may be inadvertently executing arbitrary code from the incoming PR with access to repository secrets, which would let an attacker steal repository secrets. This normally happens by running build scripts (e.g., npm build and make) or dependency installation scripts (e.g., python setup.py install). Audit your workflow file to make sure no code from the incoming PR is executed. Please see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ for additional mitigations. (link)
Prompt for AI Agents
Please address the comments from this code review:
## Security Issues

### Issue 1
<location> `.github/workflows/docs.yaml:43` </location>

<issue_to_address>
**security (yaml.github-actions.security.pull-request-target-code-checkout):** This GitHub Actions workflow file uses `pull_request_target` and checks out code from the incoming pull request. When using `pull_request_target`, the Action runs in the context of the target repository, which includes access to all repository secrets. Normally, this is safe because the Action only runs code from the target repository, not the incoming PR. However, by checking out the incoming PR code, you're now using the incoming code for the rest of the action. You may be inadvertently executing arbitrary code from the incoming PR with access to repository secrets, which would let an attacker steal repository secrets. This normally happens by running build scripts (e.g., `npm build` and `make`) or dependency installation scripts (e.g., `python setup.py install`). Audit your workflow file to make sure no code from the incoming PR is executed. Please see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ for additional mitigations.

*Source: opengrep*
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@radoering radoering merged commit 985449a into python-poetry:main Sep 12, 2025
102 of 105 checks passed
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 13, 2025
@radoering radoering deleted the update-actions branch December 13, 2025 17:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant