Skip to content

Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 20, 2025
Merged

Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152

merged 1 commit into from
Oct 20, 2025

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 20, 2025

Bumps wntrblm/nox from 2025.05.01 to 2025.10.16.

Release notes

Sourced from wntrblm/nox's releases.

2025.10.16 ⏲️

This is a quick release to make our new dependency, pbs-installer, optional. This is only needed to install Python if you are not using the uv backend. We've also added the time taken to the output when it's over a second.

We'd like to thank the following folks who contributed to this release:

Changes:

Internal:

2025.10.14 🥧

This release updates the default for the GitHub Action to target the current range of recommended Pythons (3.10-3.14). There's now a mechanism to control if nox downloads Python (even when not using uv). Several fixes include better free-threading support, custom filenames in script mode, and support for GitHub Actions Windows ARM runners.

We'd like to thank the following folks who contributed to this release:

Features:

Changes:

Bugfixes:

... (truncated)

Changelog

Sourced from wntrblm/nox's changelog.

2025.10.16

This is a quick release to make our new dependency, pbs-installer, optional. This is only needed to install Python if you are not using the uv backend. We've also added the time taken to the output when it's over a second.

We'd like to thank the following folks who contributed to this release:

Changes:

Internal:

2025.10.14

This release updates the default for the GitHub Action to target the current range of recommended Pythons (3.10-3.14). There's now a mechanism to control if nox downloads Python (even when not using uv). Several fixes include better free-threading support, custom filenames in script mode, and support for GitHub Actions Windows ARM runners.

We'd like to thank the following folks who contributed to this release:

Features:

Changes:

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump wntrblm/nox from 2025.05.01 to 2025.10.16
d920bff 
Bumps [wntrblm/nox](https://github.com/wntrblm/nox) from 2025.05.01 to 2025.10.16.
- [Release notes](https://github.com/wntrblm/nox/releases)
- [Changelog](https://github.com/wntrblm/nox/blob/main/CHANGELOG.md)
- [Commits](wntrblm/nox@2025.05.01...2025.10.16)

---
updated-dependencies:
- dependency-name: wntrblm/nox
  dependency-version: 2025.10.16
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Oct 20, 2025
@felixfontein felixfontein merged commit 3073996 into devel Oct 20, 2025
22 checks passed
@felixfontein felixfontein deleted the dependabot/github_actions/wntrblm/nox-2025.10.16 branch October 20, 2025 16:19
@felixfontein felixfontein added backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch backport-2.19 Automatically create a backport for the stable-2.19 branch backport-2.20 Automatically create a backport for the stable-2.20 branch labels Oct 20, 2025
@patchback
Copy link

patchback bot commented Oct 20, 2025 •
edited
Loading

Backport to stable-2.17: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 3073996 on top of patchback/backports/stable-2.17/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152

Backporting merged PR #3152 into devel

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it: 
    $ git remote add upstream https://github.com/ansible/ansible-documentation.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code: 
    $ git fetch upstream
$ git checkout -b patchback/backports/stable-2.17/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152 upstream/stable-2.17
  4. Now, cherry-pick PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 contents into that branch: 
    $ git cherry-pick -x 307399692c3e3f292cc940db94cd838a2ec1898e
    If it'll yell at you with something like fatal: Commit 307399692c3e3f292cc940db94cd838a2ec1898e is a merge but no -m option was given., add -m 1 as follows instead: 
    $ git cherry-pick -m1 -x 307399692c3e3f292cc940db94cd838a2ec1898e
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub: 
    $ git push origin patchback/backports/stable-2.17/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@patchback
Copy link

patchback bot commented Oct 20, 2025 •
edited
Loading

Backport to stable-2.18: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 3073996 on top of patchback/backports/stable-2.18/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152

Backporting merged PR #3152 into devel

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it: 
    $ git remote add upstream https://github.com/ansible/ansible-documentation.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code: 
    $ git fetch upstream
$ git checkout -b patchback/backports/stable-2.18/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152 upstream/stable-2.18
  4. Now, cherry-pick PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 contents into that branch: 
    $ git cherry-pick -x 307399692c3e3f292cc940db94cd838a2ec1898e
    If it'll yell at you with something like fatal: Commit 307399692c3e3f292cc940db94cd838a2ec1898e is a merge but no -m option was given., add -m 1 as follows instead: 
    $ git cherry-pick -m1 -x 307399692c3e3f292cc940db94cd838a2ec1898e
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub: 
    $ git push origin patchback/backports/stable-2.18/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@patchback
Copy link

patchback bot commented Oct 20, 2025 •
edited
Loading

Backport to stable-2.19: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 3073996 on top of patchback/backports/stable-2.19/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152

Backporting merged PR #3152 into devel

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it: 
    $ git remote add upstream https://github.com/ansible/ansible-documentation.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code: 
    $ git fetch upstream
$ git checkout -b patchback/backports/stable-2.19/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152 upstream/stable-2.19
  4. Now, cherry-pick PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 contents into that branch: 
    $ git cherry-pick -x 307399692c3e3f292cc940db94cd838a2ec1898e
    If it'll yell at you with something like fatal: Commit 307399692c3e3f292cc940db94cd838a2ec1898e is a merge but no -m option was given., add -m 1 as follows instead: 
    $ git cherry-pick -m1 -x 307399692c3e3f292cc940db94cd838a2ec1898e
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub: 
    $ git push origin patchback/backports/stable-2.19/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@patchback
Copy link

patchback bot commented Oct 20, 2025 •
edited
Loading

Backport to stable-2.20: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 3073996 on top of patchback/backports/stable-2.20/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152

Backporting merged PR #3152 into devel

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it: 
    $ git remote add upstream https://github.com/ansible/ansible-documentation.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code: 
    $ git fetch upstream
$ git checkout -b patchback/backports/stable-2.20/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152 upstream/stable-2.20
  4. Now, cherry-pick PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 contents into that branch: 
    $ git cherry-pick -x 307399692c3e3f292cc940db94cd838a2ec1898e
    If it'll yell at you with something like fatal: Commit 307399692c3e3f292cc940db94cd838a2ec1898e is a merge but no -m option was given., add -m 1 as follows instead: 
    $ git cherry-pick -m1 -x 307399692c3e3f292cc940db94cd838a2ec1898e
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Bump wntrblm/nox from 2025.05.01 to 2025.10.16 #3152 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub: 
    $ git push origin patchback/backports/stable-2.20/307399692c3e3f292cc940db94cd838a2ec1898e/pr-3152
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@oraNod
Copy link
Contributor

oraNod commented Oct 20, 2025

Thanks for the review and merge @samccann and @felixfontein I know why the backports are failing and will handle this manually for those branches.

This was referenced Oct 20, 2025
Merged
Merged
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@felixfontein felixfontein felixfontein approved these changes

@samccann samccann samccann approved these changes

@oraNod oraNod oraNod approved these changes

@gotmax23 gotmax23 Awaiting requested review from gotmax23

Assignees

No one assigned

Labels

backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch backport-2.19 Automatically create a backport for the stable-2.19 branch backport-2.20 Automatically create a backport for the stable-2.20 branch dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@oraNod @felixfontein @samccann