Skip to content

chore(deps): bump the github_actions-minor-patch group with 4 updates - #288

Merged
fastrevmd-lab merged 2 commits into
mainfrom
dependabot/github_actions/github_actions-minor-patch-f51eea2c30
Nov 21, 2026
Merged

fastrevmd-lab merged 2 commits into
mainfrom
dependabot/github_actions/github_actions-minor-patch-f51eea2c30

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the github_actions-minor-patch group with 4 updates: mechubsec/mecmcp/packaging/conformance, mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml, mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml and EmbarkStudios/cargo-deny-action.

Updates mechubsec/mecmcp/packaging/conformance from 0.32.0 to 0.33.2

Release notes

Sourced from mechubsec/mecmcp/packaging/conformance's releases.

v0.33.2

Fixed

  • ci: reusable-release-image.yml from 0.33.1 published no image whenever Docker Hub was configured. GitHub drops any job output that contains a secret's value (Skip output 'metadata' since it may contain secret), and the Docker Hub username mechub is a substring of every mechubsec image path. So the plan job's tags and labels never reached the build and merge jobs: both platforms built and pushed untagged with no labels, then the merge job refused with docker metadata produced no tags. No tag moved. The build and merge jobs now each run the metadata step, and the only job outputs left are the platform matrix, a boolean and the digest. The first real run (rustproxmoxmcp v0.12.2) caught it.

v0.33.1

Changed

  • ci: reusable-release-image.yml publishes linux/amd64 and linux/arm64 by default (rustjunosmcp#648). Apple Silicon docker pull failed with no matching manifest for linux/arm64/v8. Each platform builds on a native runner (ubuntu-24.04, ubuntu-24.04-arm) and is pushed untagged by digest. A merge job then tags one manifest list per registry and signs and verifies that list's own digest. The QEMU step is gone and any other platform is refused, because emulated builds took most of an hour per release. The smoke test runs on every platform. The digest output is now the GHCR manifest-list digest. A private caller must pass platforms: linux/amd64, since the arm64 runner is free only for public repos.

v0.33.0

Security

  • deps: rmcp 3.9.0 for RUSTSEC-2026-0462, unbounded response-body buffering in rmcp's Streamable HTTP clients (#606). Lockfile only.
  • deps: pageant 0.2.5 for GHSA-662x-8wvj-2276 (#607). pageant reaches the graph through russh on Windows targets only, so no shipped Linux binary contained it.

Fixed

  • mecmcp-changeset: a transaction whose validate() writes into the candidate can now say so with DeviceTransaction::validate_rewrites_candidate() (#612). Junos <commit-check/> gives a new system login user a uid, so every change set adding one was refused at commit with candidate changed since the caller observed it (rustjunosmcp#626). When it returns true, validate_operation re-reads the fingerprint after every validation attempt, passed or failed, and stores it in record.current; the caller passes that to the commit. Only an implementation that holds an exclusive device lock from stage through commit may return true, because a refresh without one would absorb another session's edit. The default is false, so every other vendor is unchanged. A re-read that fails leaves the operation Indeterminate with the lock held.
  • mecmcp-runtime: a consumer that sets only about and flattens a shared

... (truncated)

Changelog

Sourced from mechubsec/mecmcp/packaging/conformance'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.

How to read the entries below 0.21.0. This file was added on 2026-08-26, after 0.20.0 shipped. Those entries are reconstructed from commit subjects, so they are accurate about what changed and terse about why it mattered — unlike the hand-written notes in the sibling servers' changelogs. Where an entry is not enough, the commit range in the matching GitHub release is the source.

Two exceptions, both deliberate. The Security entries were written by hand after reading the commit bodies, because classifying by subject alone missed them and classifying by body text mislabelled two features as security fixes. And the bold prefix is the commit's scope, which is usually a crate but is sometimes an area — deps, plan, packaging, spec.

Release commits — the chore(release): X.Y.Z and bump workspace to X.Y.Z subjects that carry only a number — are omitted. Two early version bumps are kept, at 0.3.8, because their subjects record why the version moved: Workspace 0.1.6 for the ConnectInfo fix marks the release consumers had to pin past a broken rate limiter, and Bump intra-workspace dependency pins to 0.2.0 repaired dependency resolution.

Entries from 0.21.0 onward should be written by hand at release time.

[0.33.2] - 2026-11-13

Fixed

  • ci: reusable-release-image.yml from 0.33.1 published no image whenever Docker Hub was configured. GitHub drops any job output that contains a secret's value (Skip output 'metadata' since it may contain secret), and the Docker Hub username mechub is a substring of every mechubsec image path. So the plan job's tags and labels never reached the build and merge jobs: both platforms built and pushed untagged with no labels, then the merge job refused with docker metadata produced no tags. No tag moved. The build and merge jobs now each run the metadata step, and the only job outputs left are the platform matrix, a boolean and the digest. The first real run (rustproxmoxmcp v0.12.2) caught it.

[0.33.1] - 2026-11-13

Changed

  • ci: reusable-release-image.yml publishes linux/amd64 and linux/arm64 by default (rustjunosmcp#648). Apple Silicon docker pull failed with `no matching

... (truncated)

Commits
  • 78f0b97 release: v0.33.2 (#623)
  • c578863 fix(ci): stop passing image metadata through job outputs (#622)
  • 03f8142 docs(readme): current release is v0.33.1 (#620)
  • ab6786f release: v0.33.1 (#619)
  • 196353b feat(ci): multi-arch release images on native runners (rustjunosmcp#648) (#618)
  • 823f91e docs(readme): rustjunosmcp v2.7.5 (#615)
  • febe2ee docs(readme): current release is v0.33.0 (#614)
  • 256f16c release: v0.33.0 (#613)
  • 89fc171 fix(changeset): opt-in fingerprint refresh after validate; report both finger...
  • 1cad238 build(deps): axum-server 0.9.2 in mecmcp-transport (#611)
  • Additional commits viewable in compare view

Updates mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml from 0.32.0 to 0.33.2

Release notes

Sourced from mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml's releases.

v0.33.2

Fixed

  • ci: reusable-release-image.yml from 0.33.1 published no image whenever Docker Hub was configured. GitHub drops any job output that contains a secret's value (Skip output 'metadata' since it may contain secret), and the Docker Hub username mechub is a substring of every mechubsec image path. So the plan job's tags and labels never reached the build and merge jobs: both platforms built and pushed untagged with no labels, then the merge job refused with docker metadata produced no tags. No tag moved. The build and merge jobs now each run the metadata step, and the only job outputs left are the platform matrix, a boolean and the digest. The first real run (rustproxmoxmcp v0.12.2) caught it.

v0.33.1

Changed

  • ci: reusable-release-image.yml publishes linux/amd64 and linux/arm64 by default (rustjunosmcp#648). Apple Silicon docker pull failed with no matching manifest for linux/arm64/v8. Each platform builds on a native runner (ubuntu-24.04, ubuntu-24.04-arm) and is pushed untagged by digest. A merge job then tags one manifest list per registry and signs and verifies that list's own digest. The QEMU step is gone and any other platform is refused, because emulated builds took most of an hour per release. The smoke test runs on every platform. The digest output is now the GHCR manifest-list digest. A private caller must pass platforms: linux/amd64, since the arm64 runner is free only for public repos.

v0.33.0

Security

  • deps: rmcp 3.9.0 for RUSTSEC-2026-0462, unbounded response-body buffering in rmcp's Streamable HTTP clients (#606). Lockfile only.
  • deps: pageant 0.2.5 for GHSA-662x-8wvj-2276 (#607). pageant reaches the graph through russh on Windows targets only, so no shipped Linux binary contained it.

Fixed

  • mecmcp-changeset: a transaction whose validate() writes into the candidate can now say so with DeviceTransaction::validate_rewrites_candidate() (#612). Junos <commit-check/> gives a new system login user a uid, so every change set adding one was refused at commit with candidate changed since the caller observed it (rustjunosmcp#626). When it returns true, validate_operation re-reads the fingerprint after every validation attempt, passed or failed, and stores it in record.current; the caller passes that to the commit. Only an implementation that holds an exclusive device lock from stage through commit may return true, because a refresh without one would absorb another session's edit. The default is false, so every other vendor is unchanged. A re-read that fails leaves the operation Indeterminate with the lock held.
  • mecmcp-runtime: a consumer that sets only about and flattens a shared

... (truncated)

Changelog

Sourced from mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml'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.

How to read the entries below 0.21.0. This file was added on 2026-08-26, after 0.20.0 shipped. Those entries are reconstructed from commit subjects, so they are accurate about what changed and terse about why it mattered — unlike the hand-written notes in the sibling servers' changelogs. Where an entry is not enough, the commit range in the matching GitHub release is the source.

Two exceptions, both deliberate. The Security entries were written by hand after reading the commit bodies, because classifying by subject alone missed them and classifying by body text mislabelled two features as security fixes. And the bold prefix is the commit's scope, which is usually a crate but is sometimes an area — deps, plan, packaging, spec.

Release commits — the chore(release): X.Y.Z and bump workspace to X.Y.Z subjects that carry only a number — are omitted. Two early version bumps are kept, at 0.3.8, because their subjects record why the version moved: Workspace 0.1.6 for the ConnectInfo fix marks the release consumers had to pin past a broken rate limiter, and Bump intra-workspace dependency pins to 0.2.0 repaired dependency resolution.

Entries from 0.21.0 onward should be written by hand at release time.

[0.33.2] - 2026-11-13

Fixed

  • ci: reusable-release-image.yml from 0.33.1 published no image whenever Docker Hub was configured. GitHub drops any job output that contains a secret's value (Skip output 'metadata' since it may contain secret), and the Docker Hub username mechub is a substring of every mechubsec image path. So the plan job's tags and labels never reached the build and merge jobs: both platforms built and pushed untagged with no labels, then the merge job refused with docker metadata produced no tags. No tag moved. The build and merge jobs now each run the metadata step, and the only job outputs left are the platform matrix, a boolean and the digest. The first real run (rustproxmoxmcp v0.12.2) caught it.

[0.33.1] - 2026-11-13

Changed

  • ci: reusable-release-image.yml publishes linux/amd64 and linux/arm64 by default (rustjunosmcp#648). Apple Silicon docker pull failed with `no matching

... (truncated)

Commits
  • 78f0b97 release: v0.33.2 (#623)
  • c578863 fix(ci): stop passing image metadata through job outputs (#622)
  • 03f8142 docs(readme): current release is v0.33.1 (#620)
  • ab6786f release: v0.33.1 (#619)
  • 196353b feat(ci): multi-arch release images on native runners (rustjunosmcp#648) (#618)
  • 823f91e docs(readme): rustjunosmcp v2.7.5 (#615)
  • febe2ee docs(readme): current release is v0.33.0 (#614)
  • 256f16c release: v0.33.0 (#613)
  • 89fc171 fix(changeset): opt-in fingerprint refresh after validate; report both finger...
  • 1cad238 build(deps): axum-server 0.9.2 in mecmcp-transport (#611)
  • Additional commits viewable in compare view

Updates mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml from 0.32.0 to 0.33.2

Release notes

Sourced from mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml's releases.

v0.33.2

Fixed

  • ci: reusable-release-image.yml from 0.33.1 published no image whenever Docker Hub was configured. GitHub drops any job output that contains a secret's value (Skip output 'metadata' since it may contain secret), and the Docker Hub username mechub is a substring of every mechubsec image path. So the plan job's tags and labels never reached the build and merge jobs: both platforms built and pushed untagged with no labels, then the merge job refused with docker metadata produced no tags. No tag moved. The build and merge jobs now each run the metadata step, and the only job outputs left are the platform matrix, a boolean and the digest. The first real run (rustproxmoxmcp v0.12.2) caught it.

v0.33.1

Changed

  • ci: reusable-release-image.yml publishes linux/amd64 and linux/arm64 by default (rustjunosmcp#648). Apple Silicon docker pull failed with no matching manifest for linux/arm64/v8. Each platform builds on a native runner (ubuntu-24.04, ubuntu-24.04-arm) and is pushed untagged by digest. A merge job then tags one manifest list per registry and signs and verifies that list's own digest. The QEMU step is gone and any other platform is refused, because emulated builds took most of an hour per release. The smoke test runs on every platform. The digest output is now the GHCR manifest-list digest. A private caller must pass platforms: linux/amd64, since the arm64 runner is free only for public repos.

v0.33.0

Security

  • deps: rmcp 3.9.0 for RUSTSEC-2026-0462, unbounded response-body buffering in rmcp's Streamable HTTP clients (#606). Lockfile only.
  • deps: pageant 0.2.5 for GHSA-662x-8wvj-2276 (#607). pageant reaches the graph through russh on Windows targets only, so no shipped Linux binary contained it.

Fixed

  • mecmcp-changeset: a transaction whose validate() writes into the candidate can now say so with DeviceTransaction::validate_rewrites_candidate() (#612). Junos <commit-check/> gives a new system login user a uid, so every change set adding one was refused at commit with candidate changed since the caller observed it (rustjunosmcp#626). When it returns true, validate_operation re-reads the fingerprint after every validation attempt, passed or failed, and stores it in record.current; the caller passes that to the commit. Only an implementation that holds an exclusive device lock from stage through commit may return true, because a refresh without one would absorb another session's edit. The default is false, so every other vendor is unchanged. A re-read that fails leaves the operation Indeterminate with the lock held.
  • mecmcp-runtime: a consumer that sets only about and flattens a shared

... (truncated)

Changelog

Sourced from mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml'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.

How to read the entries below 0.21.0. This file was added on 2026-08-26, after 0.20.0 shipped. Those entries are reconstructed from commit subjects, so they are accurate about what changed and terse about why it mattered — unlike the hand-written notes in the sibling servers' changelogs. Where an entry is not enough, the commit range in the matching GitHub release is the source.

Two exceptions, both deliberate. The Security entries were written by hand after reading the commit bodies, because classifying by subject alone missed them and classifying by body text mislabelled two features as security fixes. And the bold prefix is the commit's scope, which is usually a crate but is sometimes an area — deps, plan, packaging, spec.

Release commits — the chore(release): X.Y.Z and bump workspace to X.Y.Z subjects that carry only a number — are omitted. Two early version bumps are kept, at 0.3.8, because their subjects record why the version moved: Workspace 0.1.6 for the ConnectInfo fix marks the release consumers had to pin past a broken rate limiter, and Bump intra-workspace dependency pins to 0.2.0 repaired dependency resolution.

Entries from 0.21.0 onward should be written by hand at release time.

[0.33.2] - 2026-11-13

Fixed

  • ci: reusable-release-image.yml from 0.33.1 published no image whenever Docker Hub was configured. GitHub drops any job output that contains a secret's value (Skip output 'metadata' since it may contain secret), and the Docker Hub username mechub is a substring of every mechubsec image path. So the plan job's tags and labels never reached the build and merge jobs: both platforms built and pushed untagged with no labels, then the merge job refused with docker metadata produced no tags. No tag moved. The build and merge jobs now each run the metadata step, and the only job outputs left are the platform matrix, a boolean and the digest. The first real run (rustproxmoxmcp v0.12.2) caught it.

[0.33.1] - 2026-11-13

Changed

  • ci: reusable-release-image.yml publishes linux/amd64 and linux/arm64 by default (rustjunosmcp#648). Apple Silicon docker pull failed with `no matching

... (truncated)

Commits
  • 78f0b97 release: v0.33.2 (#623)
  • c578863 fix(ci): stop passing image metadata through job outputs (#622)
  • 03f8142 docs(readme): current release is v0.33.1 (#620)
  • ab6786f release: v0.33.1 (#619)
  • 196353b feat(ci): multi-arch release images on native runners (rustjunosmcp#648) (#618)
  • 823f91e docs(readme): rustjunosmcp v2.7.5 (#615)
  • febe2ee docs(readme): current release is v0.33.0 (#614)
  • 256f16c release: v0.33.0 (#613)
  • 89fc171 fix(changeset): opt-in fingerprint refresh after validate; report both finger...
  • 1cad238 build(deps): axum-server 0.9.2 in mecmcp-transport (#611)
  • Additional commits viewable in compare view

Updates EmbarkStudios/cargo-deny-action from 2.1.1 to 2.1.2

Release notes

Sourced from EmbarkStudios/cargo-deny-action's releases.

Release 2.1.2 - cargo-deny 0.21.0

Fixed

  • PR#893 resolved #892 by correctly handling url matching when using IP hosts.
  • PR#895 fixed an issue where --target could not be passed multiple times in the CLI.
  • PR#885 resolved #772 by not emitting diagnostics for unused workspace dependencies when those crates were explicitly excluded from the graph by the user.
  • PR#887 resolved #707 by ignoring renamed packages when checking for workspace duplicates.
  • PR#902 resolved #898 by adding the unmatched-allow-build-script and allowed-crate-without-build-script diagnostics.
  • PR#911 resolved #910 by visiting each crate once when checking build-time dependents, so a dependency cycle no longer overflows the stack.
  • PR#915 resolved #914 by ignoring a trailing slash when exactly matching source urls, so that licenses.private.ignore-sources can match sparse registries.

Added

  • PR#899 resolved #896 by searching for configuration in .config as well.
  • PR#904 resolved #754 and #889 by adding 3 new configuration fields:
    • advisories.ignore-expiry - The default duration after the publishing of an advisory that an advisories.ignore will function for it. Once the current date surpasses that expiry the ignore will not prevent the diagnostic for the advisory being emitted. This also accepts an absolute date.
    • advisories.ignore.expiry is the same as the above, but scoped to a particular ignore. This value overrides the default.
    • advisories.ignore.allow only allows specific crates by PackageSpec to depend on the crate(s) that the advisory applies to, intended to prevent new crates or versions from being added to the graph that increase the number of edges and thus making it harder to update/remove the affected crate.
  • PR#906 changed the diagnostics for advisories and yanked crates to conditionally show the (try cargo update -p <affected crate>) and instead detect if any dependents use 1 or more version requirements that preclude updating to an unaffected/patched/unyanked version.

Deprecated

  • PR#903 deprecated the advisories.git-fetch-with-cli configuration field, which has done nothing since PR#830.
Commits

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

Bumps the github_actions-minor-patch group with 4 updates: [mechubsec/mecmcp/packaging/conformance](https://github.com/mechubsec/mecmcp), [mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml](https://github.com/mechubsec/mecmcp), [mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml](https://github.com/mechubsec/mecmcp) and [EmbarkStudios/cargo-deny-action](https://github.com/embarkstudios/cargo-deny-action).


Updates `mechubsec/mecmcp/packaging/conformance` from 0.32.0 to 0.33.2
- [Release notes](https://github.com/mechubsec/mecmcp/releases)
- [Changelog](https://github.com/mechubsec/mecmcp/blob/main/CHANGELOG.md)
- [Commits](mechubsec/mecmcp@39e7308...78f0b97)

Updates `mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml` from 0.32.0 to 0.33.2
- [Release notes](https://github.com/mechubsec/mecmcp/releases)
- [Changelog](https://github.com/mechubsec/mecmcp/blob/main/CHANGELOG.md)
- [Commits](mechubsec/mecmcp@39e7308...78f0b97)

Updates `mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml` from 0.32.0 to 0.33.2
- [Release notes](https://github.com/mechubsec/mecmcp/releases)
- [Changelog](https://github.com/mechubsec/mecmcp/blob/main/CHANGELOG.md)
- [Commits](mechubsec/mecmcp@39e7308...78f0b97)

Updates `EmbarkStudios/cargo-deny-action` from 2.1.1 to 2.1.2
- [Release notes](https://github.com/embarkstudios/cargo-deny-action/releases)
- [Commits](EmbarkStudios/cargo-deny-action@3c63498...70f8153)

---
updated-dependencies:
- dependency-name: mechubsec/mecmcp/packaging/conformance
  dependency-version: 0.33.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github_actions-minor-patch
- dependency-name: mechubsec/mecmcp/.github/workflows/reusable-registry-publish.yml
  dependency-version: 0.33.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github_actions-minor-patch
- dependency-name: mechubsec/mecmcp/.github/workflows/reusable-sign-release-tarball.yml
  dependency-version: 0.33.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github_actions-minor-patch
- dependency-name: EmbarkStudios/cargo-deny-action
  dependency-version: 2.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github_actions-minor-patch
...

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 Nov 20, 2026
@fastrevmd-lab
fastrevmd-lab merged commit 69f438f into main Nov 21, 2026
11 checks passed
@fastrevmd-lab
fastrevmd-lab deleted the dependabot/github_actions/github_actions-minor-patch-f51eea2c30 branch November 21, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant