Skip to content

Merge from master#118

Open
ikostan wants to merge 2 commits intodependabot/github_actions/dot-github/workflows/codecov/codecov-action-5.5.1from
master
Open

Merge from master#118
ikostan wants to merge 2 commits intodependabot/github_actions/dot-github/workflows/codecov/codecov-action-5.5.1from
master

Conversation

@ikostan
Copy link
Owner

@ikostan ikostan commented Sep 28, 2025

Summary by Sourcery

CI:

  • Bump actions/setup-python from v5 to v6 in all CI workflow files

dependabot bot and others added 2 commits September 4, 2025 13:47
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5 to 6.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v5...v6)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
…thub/workflows/actions/setup-python-6

Bump actions/setup-python from 5 to 6 in /.github/workflows
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Sep 28, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR merges from master and uniformly upgrades the GitHub Actions setup-python action from v5 to v6 across all CI workflows.

File-Level Changes

Change Details Files
Upgrade actions/setup-python to v6
  • Replaced uses: actions/setup-python@v5 with @v6 in each workflow
.github/workflows/flake8.yml
.github/workflows/mypy.yml
.github/workflows/pylint.yml
.github/workflows/pytest.yml
.github/workflows/rst_lint.yml
.github/workflows/snyk.yml
.github/workflows/sphinx_docs.yml
.github/workflows/sphinx_lint.yml
.github/workflows/yamllint.yml

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
Contributor

@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 - here's some feedback:

  • Pin the setup-python action to a specific commit SHA or full semantic version (e.g. v6.x.x) instead of a floating tag to avoid unexpected breakage when the action is updated upstream.
  • Consider consolidating the setup-python step into a reusable workflow or composite action so you only need to update the version in one place rather than across every CI file.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Pin the setup-python action to a specific commit SHA or full semantic version (e.g. v6.x.x) instead of a floating tag to avoid unexpected breakage when the action is updated upstream.
- Consider consolidating the setup-python step into a reusable workflow or composite action so you only need to update the version in one place rather than across every CI file.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant