Bump the github-actions group across 1 directory with 7 updates

[dependabot]

Bumps the github-actions group with 7 updates in the / directory:

Package	From	To
github/codeql-action/init	4.37.3	4.37.5
github/codeql-action/autobuild	4.37.3	4.37.5
github/codeql-action/analyze	4.37.3	4.37.5
CodSpeedHQ/action	4.18.5	5.0.2
pypa/gh-action-pypi-publish	1.14.1	1.14.2
docker/login-action	4.4.0	4.6.0
anthropics/claude-code-action	1.0.181	1.0.183

Updates github/codeql-action/init from 4.37.3 to 4.37.5

Release notes

Sourced from github/codeql-action/init's releases.

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

Changelog

Sourced from github/codeql-action/init's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

No user facing changes.

4.36.2 - 04 Jun 2026

• Cache CodeQL CLI version information across Actions steps. #3943
• Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
• Update default CodeQL bundle version to 2.25.6. #3948

... (truncated)

Commits

• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• e74600b Update changelog for v4.37.5
• 1cd4d01 Merge pull request #4061 from github/henrymercer/turbo-system
• d2bfc30 Merge pull request #4050 from github/mbg/status/registries
• 68028fc Merge pull request #4062 from github/sam-robson/migrate-enterprise-release-pat
• c29563e ci: use federated enterprise release PAT
• 155e522 Link the PR from the changelog entry
• 2d3b351 Handle network errors when streaming the CodeQL bundle download
• 5d3eb98 Merge pull request #4055 from github/dependabot/npm_and_yarn/npm-minor-203262...
• c5f739b Merge branch 'main' into dependabot/npm_and_yarn/npm-minor-2032624187
• Additional commits viewable in compare view

Updates github/codeql-action/autobuild from 4.37.3 to 4.37.5

Release notes

Sourced from github/codeql-action/autobuild's releases.

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

Changelog

Sourced from github/codeql-action/autobuild's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

No user facing changes.

4.36.2 - 04 Jun 2026

• Cache CodeQL CLI version information across Actions steps. #3943
• Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
• Update default CodeQL bundle version to 2.25.6. #3948

... (truncated)

Commits

• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• e74600b Update changelog for v4.37.5
• 1cd4d01 Merge pull request #4061 from github/henrymercer/turbo-system
• d2bfc30 Merge pull request #4050 from github/mbg/status/registries
• 68028fc Merge pull request #4062 from github/sam-robson/migrate-enterprise-release-pat
• c29563e ci: use federated enterprise release PAT
• 155e522 Link the PR from the changelog entry
• 2d3b351 Handle network errors when streaming the CodeQL bundle download
• 5d3eb98 Merge pull request #4055 from github/dependabot/npm_and_yarn/npm-minor-203262...
• c5f739b Merge branch 'main' into dependabot/npm_and_yarn/npm-minor-2032624187
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.37.3 to 4.37.5

Release notes

Sourced from github/codeql-action/analyze's releases.

v4.37.5

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

v4.37.4

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

Changelog

Sourced from github/codeql-action/analyze's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

No user facing changes.

4.36.2 - 04 Jun 2026

• Cache CodeQL CLI version information across Actions steps. #3943
• Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
• Update default CodeQL bundle version to 2.25.6. #3948

... (truncated)

Commits

• d1ba80a Merge pull request #4067 from github/update-v4.37.5-1cd4d01d5
• e74600b Update changelog for v4.37.5
• 1cd4d01 Merge pull request #4061 from github/henrymercer/turbo-system
• d2bfc30 Merge pull request #4050 from github/mbg/status/registries
• 68028fc Merge pull request #4062 from github/sam-robson/migrate-enterprise-release-pat
• c29563e ci: use federated enterprise release PAT
• 155e522 Link the PR from the changelog entry
• 2d3b351 Handle network errors when streaming the CodeQL bundle download
• 5d3eb98 Merge pull request #4055 from github/dependabot/npm_and_yarn/npm-minor-203262...
• c5f739b Merge branch 'main' into dependabot/npm_and_yarn/npm-minor-2032624187
• Additional commits viewable in compare view

Updates CodSpeedHQ/action from 4.18.5 to 5.0.2

Release notes

Sourced from CodSpeedHQ/action's releases.

v5.0.2

What's Changed

• feat: add cycle-estimation and exclude-allocations inputs by @​not-matthias in CodSpeedHQ/action#229

Full Changelog: CodSpeedHQ/action@v5.0.1...v5.0.2

v5.0.1

🚀 Highlights

More precise measurements by default

cycle-estimation is now enabled by default, giving more precise benchmark cycle estimation in Simulation mode. See docs.

New: allocation exclusion

Opt in to exclude-allocations to remove allocator time from benchmarks in Simulation mode and reduce variance. See docs.

samply-based profiler by default on Linux

The walltime profiler now uses samply on all OSes. Set CODSPEED_WALLTIME_PROFILER=perf to restore the previous behavior.

⚠️ Breaking changes

• cycle-estimation is now enabled by default (see above)
• The samply-based profiler is now the default on Linux; set CODSPEED_WALLTIME_PROFILER=perf to revert

Details

🚀 Features

• Load eBPF through a delegated BPF token by @​GuillaumeLagrange
• Enable cycle estimation and allocation exclusion by default by @​not-matthias in #461
• Make samply profiler default for all OSes (#472) by @​GuillaumeLagrange in #475

🐛 Bug Fixes

• Classify mapped libraries without init-userns privilege by @​GuillaumeLagrange
• Disable allocator exclusion by default (#489) by @​not-matthias in #489

💼 Other

• Bump the memtrack pin to 1.4.0 by @​adriencaccia in #484

🏗️ Refactor

• Hook-based CPU isolation for the walltime runner by @​GuillaumeLagrange

🧪 Testing

• Run every tracking test under both BPF variants by @​GuillaumeLagrange

⚙️ Internals

• chore: bump runner version to 5.0.1 by @​github-actions[bot] in CodSpeedHQ/action#228
• docs: bump documented action version to v5 by @​adriencaccia in CodSpeedHQ/action#227
• Bump submodule to reduce debug info server timeouts by @​GuillaumeLagrange
• Make tests run release builds of the binaries by @​GuillaumeLagrange in #456
• Update submodule to fix fmt and ignore ubuntu debuginfod serv by @​GuillaumeLagrange

... (truncated)

Commits

• 0ca9cbb Release v5.0.2 🚀
• 551137a ci: restrict GITHUB_TOKEN to contents: read
• fc63264 feat: add cycle-estimation and exclude-allocations inputs
• 8847237 Release v5.0.1 🚀
• 81795c3 fix: remove yanked 5.0.0 version hash
• eaace14 docs: bump documented action version to v5
• a3e4fe0 chore: bump runner version to 5.0.1
• f87ba88 Release v5.0.0 🚀
• 7ab72f2 chore: bump runner version to 5.0.0
• f22792b Release v4.19.1 🚀
• Additional commits viewable in compare view

Updates pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

v1.14.2

🛠️ Urgh… Another release!? Again? Explain yourself!

Looking at the diff, you'll only witness updates across the dependency tree. That's it! It's not a security fix or anything like that even, no. But you'll want this update.

[!tip] So what most people will find useful is @​takluyver💰's update of Twine to v7 that we use internally (#416). This version will let them upload their sdists and wheels containing core packaging metadata v2.5 to (Test)PyPI.

🧐 Tell me why..

TL;DR non-pure-python projects with C-extensions tend to have dozens (sometimes hundreds) wheels to upload to PyPI per release. They are often quite big and take time to transfer over the network. People started noticing problems and coming up with DIY sharding workarounds like aio-libs/aiohttp#13226 around July 23. On this date, projects with a good amount of bytes to publish would start getting timeouts 5 minutes after the PyPI publishing job begun. The same job that worked just fine before.

I had to start pinging upstream library and ecosystem people, on GitHub and privately, to start making sense of what was happening. Eventually, we collectively concluded that GitHub must've shortened the lifetime of their OIDC identity — it seems to have used to be 10 minutes long (at some point in the past) and is now 5 minutes, apparently. It's not documented clearly, and we have not been able to get any clarity by attempting to contact GitHub through private channels, using personal connections.

Over the course of investigation, @​facutuesca💰 found and fixed a related underlying cache invalidation bug in sigstore/sigstore-python#1838, which he then coordinated propagation through the dependency chain updates in sigstore-python, pypi-attestations, gh-action-pypi-publish and gh-action-sigstore-python.

Mike's also discovered that Sigstore's Rekor slowdown seems to have become the main contributing cause of the last week's incident. He's collected some data to support this claim: https://publishing-five-minute-timeout.tiiny.site.

🫶 New Contributors

• @​davidbrochart made their first contribution in #415
• @​takluyver made their first contribution in #416

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.1...v1.14.2

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

🙏 Special Thanks to @​davidbrochart💰 and @​Dreamsorcerer💰 for turning my attention (in #415 and in private) to the newly surfaced corner case in GitHub's behavior that only affected a narrow category of projects while many others remained blissfully unaware. @​bdraco💰 came up with a DIY sharding workaround for aiohttp that served as a demo for other projects. @​miketheman💰 confirmed the Warehouse-side details. Also, @​jku💰 and @​woodruffw💰 helped work through, review and release the Sigstore ecosystem upstream libs.

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and [on GitHub][release discussion].

[![GH Sponsors badge]][GH Sponsors URL]

... (truncated)

Commits

• dc37677 Merge pull request #417 from trail-of-forks/ft/bump-deps
• 8b2f234 Bump pypi-attestations and sigstore
• 78b72db Merge pull request #416 from takluyver/twine-v7
• 92f4d2a Update twine to v7
• See full diff in compare view

Updates docker/login-action from 4.4.0 to 4.6.0

Release notes

Sourced from docker/login-action's releases.

v4.6.0

• Harden buildx scoped config path handling by @​crazy-max in docker/login-action#1059
• Bump @​aws-sdk/client-ecr and @​aws-sdk/client-ecr-public to 3.1095.0 in docker/login-action#1051
• Bump js-yaml from 5.2.1 to 5.2.2 in docker/login-action#1057
• Bump postcss from 8.5.10 to 8.5.22 in docker/login-action#1056

Full Changelog: docker/login-action@v4.5.2...v4.6.0

v4.5.2

• Surface Docker Hub OIDC error responses by @​crazy-max in docker/login-action#1058

Full Changelog: docker/login-action@v4.5.1...v4.5.2

v4.5.1

• Support dhi.io as Docker Hub OIDC registry by @​crazy-max in docker/login-action#1054

Full Changelog: docker/login-action@v4.5.0...v4.5.1

v4.5.0

• Docker Hub OIDC login support by @​crazy-max in docker/login-action#1048
• Bump @​aws-sdk/client-ecr and @​aws-sdk/client-ecr-public to 3.1091.0 in docker/login-action#1037
• Bump @​docker/actions-toolkit from 0.92.0 to 0.94.0 in docker/login-action#1044 docker/login-action#1050
• Bump brace-expansion from 1.1.13 to 1.1.16 in docker/login-action#1046
• Bump js-yaml from 5.2.0 to 5.2.1 in docker/login-action#1038

Full Changelog: docker/login-action@v4.4.0...v4.5.0

Commits

• dbcb813 Merge pull request #1051 from docker/dependabot/npm_and_yarn/aws-sdk-dependen...
• 5bcb015 [dependabot skip] chore: update generated content
• b30b2f2 build(deps): bump the aws-sdk-dependencies group across 1 directory with 2 up...
• 9087f1e Merge pull request #1057 from docker/dependabot/npm_and_yarn/js-yaml-5.2.2
• 0009830 [dependabot skip] chore: update generated content
• 2325523 build(deps): bump js-yaml from 5.2.1 to 5.2.2
• 4ec1d4a Merge pull request #1056 from docker/dependabot/npm_and_yarn/postcss-8.5.22
• 5fc99ba Merge pull request #1053 from docker/dependabot/github_actions/aws-actions/co...
• e512bd5 Merge pull request #1052 from docker/dependabot/github_actions/codeql-actions...
• a146c91 Merge pull request #1059 from crazy-max/harden-buildx-scope-paths
• Additional commits viewable in compare view

Updates anthropics/claude-code-action from 1.0.181 to 1.0.183

Release notes

Sourced from anthropics/claude-code-action's releases.

v1.0.183

Full Changelog: anthropics/claude-code-action@v1...v1.0.183

v1.0.182

Full Changelog: anthropics/claude-code-action@v1...v1.0.182

Commits

• be7b93b chore: bump Claude Code to 2.1.220 and Agent SDK to 0.3.220
• e0cf66d chore: bump Claude Code to 2.1.219 and Agent SDK to 0.3.219
• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.