Skip to content

chore: bump the all-github-actions group across 1 directory with 4 updates - #448

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/all-github-actions-131a838c23
Open

chore: bump the all-github-actions group across 1 directory with 4 updates#448
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/all-github-actions-131a838c23

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the all-github-actions group with 4 updates in the / directory: astral-sh/setup-uv, actions/setup-node, RijksICTGilde/zad-actions/deploy and RijksICTGilde/zad-actions/cleanup.

Updates astral-sh/setup-uv from 10.2.0 to 10.3.3

Release notes

Sourced from astral-sh/setup-uv's releases.

v10.3.3 🌈 Use Astral mirror for version manifests with GitHub fallback

Changes

This release contains something that should have been included a very long time ago. Sorry for sleeping on that.

This action now retrieves the release manifest that contains the available versions, their download links and checksums from the Astral mirror, rather than trying GitHub first. This should present much more stable. (Known checksums are still checked, so the security impact does not change)

Also a big thank you to @​soujasK for a set of bugfixes 👏

🐛 Bug fixes

🧰 Maintenance

📚 Documentation

v10.3.2 🌈 update known checksums for 0.13.5

Changes

🧰 Maintenance

📚 Documentation

v10.3.1 🌈 preserve cache error class names in save-cache bundle

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes

🧰 Maintenance

... (truncated)

Commits
  • 68559e9 Use Astral mirror for version manifests with GitHub fallback (#1119)
  • 0192b69 chore: update known checksums for 0.13.6 (#1117)
  • 2f29784 docs: use JSDoc for compatible release specifier comment (#1113)
  • 9c73321 fix: allow whitespace in uv requirement specifiers (#1112)
  • 80fbe01 fix: resolve ~= specifiers with PEP 440 semantics (#1111)
  • 36b7b57 fix: only report a saved cache when saving succeeded (#1110)
  • 56618ca docs: update version references to v10.3.2 (#1104)
  • 07a047e chore: update known checksums for 0.13.5 (#1103)
  • e1b8536 docs: update version references to v10.3.1 (#1102)
  • 18d369b chore(deps): roll up Dependabot updates (#1101)
  • Additional commits viewable in compare view

Updates actions/setup-node from 6 to 7

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency update:

New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v6.5.0

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

v6.4.0

What's Changed

Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.4.0

v6.3.0

What's Changed

Enhancements:

... (truncated)

Commits
  • 949feb2 Bump eslint from 10.5.0 to 10.11.0 and package.json from 7.0.0 to 7.1.0 (#1635)
  • 7207c4f chore: update dependencies and add license files (#1642)
  • 54337e0 Bump eslint-plugin-n from 18.1.0 to 18.3.0 (#1638)
  • fb54fa8 Bump jest-each from 30.4.1 to 30.5.2 (#1636)
  • 7f84f1d Bump pnpm/action-setup from 6.0.10 to 6.1.0 (#1631)
  • 0c54c7b Bump @​typescript-eslint/parser from 8.62.0 to 8.70.0 (#1615)
  • a829419 Bump @​types/semver from 7.7.1 to 7.8.0 (#1616)
  • 680d1e4 Support absolute paths in node-version-file (#1633)
  • db0fb3a Bump baseline-browser-mapping from 2.10.38 to 2.11.22 (#1629)
  • 94196ee Bump pnpm/action-setup from 6.0.9 to 6.0.10 (#1602)
  • Additional commits viewable in compare view

Updates RijksICTGilde/zad-actions/deploy from 4.2.0 to 4.4.0

Release notes

Sourced from RijksICTGilde/zad-actions/deploy's releases.

v4.4.0

Added

  • deploy: input fail-on-warnings (default false). Operations Manager can accept a rollout and still report that components are unhealthy, for instance when the registry could not deliver an image. zad-cli prints that as a warning on stderr and exits 0, so the step went green on a deployment that never came up, and the failure surfaced later in whatever depended on it. With fail-on-warnings: 'true' the action passes --strict and fails the step, with each warning's headline, summary, details and next steps as an error annotation. When the rollout is handed over to another task, the action reads that task's final result itself, since zad task wait does not surface warnings, and reports it with the same log lines and suggestions a direct rollout shows; failures the result names for another deployment do not count
  • deploy: without fail-on-warnings, those warnings become warning annotations instead of plain log lines, so they show up in the run summary

Changed

  • deploy, cleanup and scheduled-cleanup: astral-sh/setup-uv from v6 to v7

What's Changed

New Contributors

Full Changelog: RijksICTGilde/zad-actions@v4.3.2...v4.4.0

v4.3.2

Fixed

  • deploy, cleanup and scheduled-cleanup: pin uv to 0.12.17 in the setup-uv step. Without a version, setup-uv resolves "latest" through the GitHub API whenever the caller's workspace root has no uv.toml or pyproject.toml; on a Forgejo runner github.token is not valid there, so the lookup ran anonymously and failed intermittently on the rate limit
  • deploy, cleanup and scheduled-cleanup: turn off the setup-uv cache. uv only installs zad-cli here, so the cache had nothing to hold and every run warned that its dependency glob matched no files

Internal

  • Dependabot also scans deploy/, cleanup/ and scheduled-cleanup/. With only / it read .github/workflows and a root action.yml, so the actions the composite actions pull in (such as astral-sh/setup-uv) never got an update
  • yamllint runs with --strict from a shared .yamllint.yaml, in pre-commit and CI alike; CI now lints every YAML file instead of a hand-picked list that missed scheduled-cleanup. .editorconfig sets the same 150-column limit for YAML
  • The pre-commit.ci settings moved into .pre-commit-config.yaml: pre-commit.ci only reads the ci: key there, so .pre-commit-ci.yaml was ignored
  • The smoke tests pass skip-bot-prs: 'false' to every action call. On its default the actions skip themselves when the PR author is a bot, so every assertion read an empty output and the suite went red on a Dependabot PR while testing nothing. Now that Dependabot scans the composite actions, that is every bump it opens. A bot-check job holds the skip logic itself, against the step's own script: a PR author cannot be faked in a workflow event, so it is extracted the way deploy-log extracts the deploy step

What's Changed

Full Changelog: RijksICTGilde/zad-actions@v4.3.1...v4.3.2

v4.3.1

Changed

  • The plugin and the actions share one version line. .plugin/plugin.json had stood at 1.2.0 since February while the actions moved through four minors to 4.3.0, so the marketplace installed a plugin that claimed a version from before seven commits and 597 lines of skill changes. The plugin version is now the tag version, which makes the marketplace follow a release of either without anyone remembering a second number
  • The five skills no longer pin model: sonnet. A pinned model overrides the choice of whoever runs the skill, which is wrong for reference content: these skills describe ZAD deployment, linting and releases, they are not an agent loop with a cost or latency profile worth constraining. Nothing measured that sonnet was sufficient here, and a hardcoded model name is five places to edit when the naming changes, with nothing to signal that it went stale. The six plugins in the developer.overheid.nl marketplace dropped theirs for the same reason

... (truncated)

Changelog

Sourced from RijksICTGilde/zad-actions/deploy's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Documentation

  • README: how to deploy to another ZAD cluster, such as staging, with api-base-url

[4.4.0] - 2026-10-23

Added

  • deploy: input fail-on-warnings (default false). Operations Manager can accept a rollout and still report that components are unhealthy, for instance when the registry could not deliver an image. zad-cli prints that as a warning on stderr and exits 0, so the step went green on a deployment that never came up, and the failure surfaced later in whatever depended on it. With fail-on-warnings: 'true' the action passes --strict and fails the step, with each warning's headline, summary, details and next steps as an error annotation. When the rollout is handed over to another task, the action reads that task's final result itself, since zad task wait does not surface warnings, and reports it with the same log lines and suggestions a direct rollout shows; failures the result names for another deployment do not count
  • deploy: without fail-on-warnings, those warnings become warning annotations instead of plain log lines, so they show up in the run summary

Changed

  • deploy, cleanup and scheduled-cleanup: astral-sh/setup-uv from v6 to v7

[4.3.2] - 2026-10-08

Fixed

  • deploy, cleanup and scheduled-cleanup: pin uv to 0.12.17 in the setup-uv step. Without a version, setup-uv resolves "latest" through the GitHub API whenever the caller's workspace root has no uv.toml or pyproject.toml; on a Forgejo runner github.token is not valid there, so the lookup ran anonymously and failed intermittently on the rate limit
  • deploy, cleanup and scheduled-cleanup: turn off the setup-uv cache. uv only installs zad-cli here, so the cache had nothing to hold and every run warned that its dependency glob matched no files

Internal

  • Dependabot also scans deploy/, cleanup/ and scheduled-cleanup/. With only / it read .github/workflows and a root action.yml, so the actions the composite actions pull in (such as astral-sh/setup-uv) never got an update
  • yamllint runs with --strict from a shared .yamllint.yaml, in pre-commit and CI alike; CI now lints every YAML file instead of a hand-picked list that missed scheduled-cleanup. .editorconfig sets the same 150-column limit for YAML
  • The pre-commit.ci settings moved into .pre-commit-config.yaml: pre-commit.ci only reads the ci: key there, so .pre-commit-ci.yaml was ignored
  • The smoke tests pass skip-bot-prs: 'false' to every action call. On its default the actions skip themselves when the PR author is a bot, so every assertion read an empty output and the suite went red on a Dependabot PR while testing nothing. Now that Dependabot scans the composite actions, that is every bump it opens. A bot-check job holds the skip logic itself, against the step's own script: a PR author cannot be faked in a workflow event, so it is extracted the way deploy-log extracts the deploy step

[4.3.1] - 2026-10-07

Changed

  • The plugin and the actions share one version line. .plugin/plugin.json had stood at 1.2.0 since February while the actions moved through four minors to 4.3.0, so the marketplace installed a plugin that claimed a version from before seven commits and 597 lines of skill changes. The plugin version is now the tag version, which makes the marketplace follow a release of either without anyone remembering a second number
  • The five skills no longer pin model: sonnet. A pinned model overrides the choice of whoever runs the skill, which is wrong for reference content: these skills describe ZAD deployment, linting and releases, they are not an agent loop with a cost or latency profile worth constraining. Nothing measured that sonnet was sufficient here, and a hardcoded model name is five places to edit when the naming changes, with nothing to signal that it went stale. The six plugins in the developer.overheid.nl marketplace dropped theirs for the same reason

Internal

  • scripts/bump_version.py sets the version in .plugin/plugin.json and regenerates the two platform manifests, so the three cannot drift apart by hand
  • The release workflow refuses a tag whose version does not match .plugin/plugin.json, and names the helper in the error. A forgotten bump now fails the release before it publishes, instead of shipping a plugin that claims an older version — which is how the 1.2.0 gap went unnoticed for six months. The check runs before the release is created, so the existing rollback step takes the tag back down

[4.3.0] - 2026-10-07

Upgrading

A deploy step can now fail where it used to pass, in two cases, both of which were a green step over a rollout that had not happened:

  • The deployment task was handed over to a newer task covering its deployment scope, and that task ended failed or cancelled. Previously the hand-over was invisible and the step reported success over addresses that nothing answered on; it now fails and names the task.
  • The hand-over ended with changes saved but not rolled out. The step fails with the count and zad project refresh, rather than publishing addresses the project file asks for.

... (truncated)

Commits
  • 4217cea chore: release 4.4.0 (#78)
  • c63759c feat(deploy): fail-on-warnings input (#77)
  • cc0b1fa chore(deps): bump the actions group across 3 directories with 1 update (#74)
  • b612e59 chore: release 4.3.2 (#76)
  • f481d3d test: let the smoke suite run on a bot's pull request (#75)
  • 7b466a4 chore(lint): run yamllint strict, same config locally and in CI (#66)
  • 0b62a32 chore(deps): let Dependabot scan the composite actions (#65)
  • cf1e525 fix: pin uv version in setup-uv steps (#64)
  • 428dc1e chore(release): neem de model-pin wijziging mee in 4.3.1 (#73)
  • f9eadda chore: verwijder model-pin uit de skills (#72)
  • Additional commits viewable in compare view

Updates RijksICTGilde/zad-actions/cleanup from 4.2.0 to 4.4.0

Release notes

Sourced from RijksICTGilde/zad-actions/cleanup's releases.

v4.4.0

Added

  • deploy: input fail-on-warnings (default false). Operations Manager can accept a rollout and still report that components are unhealthy, for instance when the registry could not deliver an image. zad-cli prints that as a warning on stderr and exits 0, so the step went green on a deployment that never came up, and the failure surfaced later in whatever depended on it. With fail-on-warnings: 'true' the action passes --strict and fails the step, with each warning's headline, summary, details and next steps as an error annotation. When the rollout is handed over to another task, the action reads that task's final result itself, since zad task wait does not surface warnings, and reports it with the same log lines and suggestions a direct rollout shows; failures the result names for another deployment do not count
  • deploy: without fail-on-warnings, those warnings become warning annotations instead of plain log lines, so they show up in the run summary

Changed

  • deploy, cleanup and scheduled-cleanup: astral-sh/setup-uv from v6 to v7

What's Changed

New Contributors

Full Changelog: RijksICTGilde/zad-actions@v4.3.2...v4.4.0

v4.3.2

Fixed

  • deploy, cleanup and scheduled-cleanup: pin uv to 0.12.17 in the setup-uv step. Without a version, setup-uv resolves "latest" through the GitHub API whenever the caller's workspace root has no uv.toml or pyproject.toml; on a Forgejo runner github.token is not valid there, so the lookup ran anonymously and failed intermittently on the rate limit
  • deploy, cleanup and scheduled-cleanup: turn off the setup-uv cache. uv only installs zad-cli here, so the cache had nothing to hold and every run warned that its dependency glob matched no files

Internal

  • Dependabot also scans deploy/, cleanup/ and scheduled-cleanup/. With only / it read .github/workflows and a root action.yml, so the actions the composite actions pull in (such as astral-sh/setup-uv) never got an update
  • yamllint runs with --strict from a shared .yamllint.yaml, in pre-commit and CI alike; CI now lints every YAML file instead of a hand-picked list that missed scheduled-cleanup. .editorconfig sets the same 150-column limit for YAML
  • The pre-commit.ci settings moved into .pre-commit-config.yaml: pre-commit.ci only reads the ci: key there, so .pre-commit-ci.yaml was ignored
  • The smoke tests pass skip-bot-prs: 'false' to every action call. On its default the actions skip themselves when the PR author is a bot, so every assertion read an empty output and the suite went red on a Dependabot PR while testing nothing. Now that Dependabot scans the composite actions, that is every bump it opens. A bot-check job holds the skip logic itself, against the step's own script: a PR author cannot be faked in a workflow event, so it is extracted the way deploy-log extracts the deploy step

What's Changed

Full Changelog: RijksICTGilde/zad-actions@v4.3.1...v4.3.2

v4.3.1

Changed

  • The plugin and the actions share one version line. .plugin/plugin.json had stood at 1.2.0 since February while the actions moved through four minors to 4.3.0, so the marketplace installed a plugin that claimed a version from before seven commits and 597 lines of skill changes. The plugin version is now the tag version, which makes the marketplace follow a release of either without anyone remembering a second number
  • The five skills no longer pin model: sonnet. A pinned model overrides the choice of whoever runs the skill, which is wrong for reference content: these skills describe ZAD deployment, linting and releases, they are not an agent loop with a cost or latency profile worth constraining. Nothing measured that sonnet was sufficient here, and a hardcoded model name is five places to edit when the naming changes, with nothing to signal that it went stale. The six plugins in the developer.overheid.nl marketplace dropped theirs for the same reason

... (truncated)

Changelog

Sourced from RijksICTGilde/zad-actions/cleanup's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Documentation

  • README: how to deploy to another ZAD cluster, such as staging, with api-base-url

[4.4.0] - 2026-10-23

Added

  • deploy: input fail-on-warnings (default false). Operations Manager can accept a rollout and still report that components are unhealthy, for instance when the registry could not deliver an image. zad-cli prints that as a warning on stderr and exits 0, so the step went green on a deployment that never came up, and the failure surfaced later in whatever depended on it. With fail-on-warnings: 'true' the action passes --strict and fails the step, with each warning's headline, summary, details and next steps as an error annotation. When the rollout is handed over to another task, the action reads that task's final result itself, since zad task wait does not surface warnings, and reports it with the same log lines and suggestions a direct rollout shows; failures the result names for another deployment do not count
  • deploy: without fail-on-warnings, those warnings become warning annotations instead of plain log lines, so they show up in the run summary

Changed

  • deploy, cleanup and scheduled-cleanup: astral-sh/setup-uv from v6 to v7

[4.3.2] - 2026-10-08

Fixed

  • deploy, cleanup and scheduled-cleanup: pin uv to 0.12.17 in the setup-uv step. Without a version, setup-uv resolves "latest" through the GitHub API whenever the caller's workspace root has no uv.toml or pyproject.toml; on a Forgejo runner github.token is not valid there, so the lookup ran anonymously and failed intermittently on the rate limit
  • deploy, cleanup and scheduled-cleanup: turn off the setup-uv cache. uv only installs zad-cli here, so the cache had nothing to hold and every run warned that its dependency glob matched no files

Internal

  • Dependabot also scans deploy/, cleanup/ and scheduled-cleanup/. With only / it read .github/workflows and a root action.yml, so the actions the composite actions pull in (such as astral-sh/setup-uv) never got an update
  • yamllint runs with --strict from a shared .yamllint.yaml, in pre-commit and CI alike; CI now lints every YAML file instead of a hand-picked list that missed scheduled-cleanup. .editorconfig sets the same 150-column limit for YAML
  • The pre-commit.ci settings moved into .pre-commit-config.yaml: pre-commit.ci only reads the ci: key there, so .pre-commit-ci.yaml was ignored
  • The smoke tests pass skip-bot-prs: 'false' to every action call. On its default the actions skip themselves when the PR author is a bot, so every assertion read an empty output and the suite went red on a Dependabot PR while testing nothing. Now that Dependabot scans the composite actions, that is every bump it opens. A bot-check job holds the skip logic itself, against the step's own script: a PR author cannot be faked in a workflow event, so it is extracted the way deploy-log extracts the deploy step

[4.3.1] - 2026-10-07

Changed

  • The plugin and the actions share one version line. .plugin/plugin.json had stood at 1.2.0 since February while the actions moved through four minors to 4.3.0, so the marketplace installed a plugin that claimed a version from before seven commits and 597 lines of skill changes. The plugin version is now the tag version, which makes the marketplace follow a release of either without anyone remembering a second number
  • The five skills no longer pin model: sonnet. A pinned model overrides the choice of whoever runs the skill, which is wrong for reference content: these skills describe ZAD deployment, linting and releases, they are not an agent loop with a cost or latency profile worth constraining. Nothing measured that sonnet was sufficient here, and a hardcoded model name is five places to edit when the naming changes, with nothing to signal that it went stale. The six plugins in the developer.overheid.nl marketplace dropped theirs for the same reason

Internal

  • scripts/bump_version.py sets the version in .plugin/plugin.json and regenerates the two platform manifests, so the three cannot drift apart by hand
  • The release workflow refuses a tag whose version does not match .plugin/plugin.json, and names the helper in the error. A forgotten bump now fails the release before it publishes, instead of shipping a plugin that claims an older version — which is how the 1.2.0 gap went unnoticed for six months. The check runs before the release is created, so the existing rollback step takes the tag back down

[4.3.0] - 2026-10-07

Upgrading

A deploy step can now fail where it used to pass, in two cases, both of which were a green step over a rollout that had not happened:

  • The deployment task was handed over to a newer task covering its deployment scope, and that task ended failed or cancelled. Previously the hand-over was invisible and the step reported success over addresses that nothing answered on; it now fails and names the task.
  • The hand-over ended with changes saved but not rolled out. The step fails with the count and zad project refresh, rather than publishing addresses the project file asks for.

... (truncated)

Commits
  • 4217cea chore: release 4.4.0 (#78)
  • c63759c feat(deploy): fail-on-warnings input (#77)
  • cc0b1fa chore(deps): bump the actions group across 3 directories with 1 update (#74)
  • b612e59 chore: release 4.3.2 (#76)
  • f481d3d test: let the smoke suite run on a bot's pull request (#75)
  • 7b466a4 chore(lint): run yamllint strict, same config locally and in CI (#66)
  • 0b62a32 chore(deps): let Dependabot scan the composite actions (#65)
  • cf1e525 fix: pin uv version in setup-uv steps (#64)
  • 428dc1e chore(release): neem de model-pin wijziging mee in 4.3.1 (#73)
  • f9eadda chore: verwijder model-pin uit de skills (#72)
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from a team as a code owner October 16, 2026 08:05
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Oct 16, 2026
@dependabot dependabot Bot changed the title chore: bump the all-github-actions group with 4 updates chore: bump the all-github-actions group across 1 directory with 4 updates Oct 30, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/all-github-actions-131a838c23 branch 2 times, most recently from 5e42bcb to 6810d6d Compare November 5, 2026 12:33
@dependabot
chore: bump the all-github-actions group across 1 directory with 4 up…
fd5df0d 
…dates

Bumps the all-github-actions group with 4 updates in the / directory: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv), [actions/setup-node](https://github.com/actions/setup-node), [RijksICTGilde/zad-actions/deploy](https://github.com/rijksictgilde/zad-actions) and [RijksICTGilde/zad-actions/cleanup](https://github.com/rijksictgilde/zad-actions).


Updates `astral-sh/setup-uv` from 10.2.0 to 10.3.3
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@c18668a...68559e9)

Updates `actions/setup-node` from 6 to 7
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v6...v7)

Updates `RijksICTGilde/zad-actions/deploy` from 4.2.0 to 4.4.0
- [Release notes](https://github.com/rijksictgilde/zad-actions/releases)
- [Changelog](https://github.com/RijksICTGilde/zad-actions/blob/main/CHANGELOG.md)
- [Commits](RijksICTGilde/zad-actions@4ac541a...4217cea)

Updates `RijksICTGilde/zad-actions/cleanup` from 4.2.0 to 4.4.0
- [Release notes](https://github.com/rijksictgilde/zad-actions/releases)
- [Changelog](https://github.com/RijksICTGilde/zad-actions/blob/main/CHANGELOG.md)
- [Commits](RijksICTGilde/zad-actions@4ac541a...4217cea)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: all-github-actions
- dependency-name: astral-sh/setup-uv
  dependency-version: 10.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: all-github-actions
- dependency-name: RijksICTGilde/zad-actions/cleanup
  dependency-version: 4.3.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: all-github-actions
- dependency-name: RijksICTGilde/zad-actions/deploy
  dependency-version: 4.3.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: all-github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/all-github-actions-131a838c23 branch from 6810d6d to fd5df0d Compare November 6, 2026 09:06

This branch has not been deployed

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

Reviewers

No reviews

Assignees

No one assigned

Labels

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.

0 participants