Skip to content

chore(deps): bump the github_actions-minor-patch group with 3 updates - #282

Merged
fastrevmd-lab merged 2 commits into
mainfrom
dependabot/github_actions/github_actions-minor-patch-1a25eeab44
Nov 14, 2026
Merged

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

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

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

Release notes

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

v0.32.0

Fixed

  • ci: reusable-release-image.yml Verify signatures (hard gate) now retries each ref's cosign verify (6 attempts, backoff 2/4/8/15/30 s, about 59 s) before failing. Docker Hub's referrers index is eventually consistent, so verify right after signing could report no signatures found and fail the release (seen on rustsdcmcp v0.6.0). The gate stays hard: a signature that never appears still fails the job with cosign's last error. Consumers pin this workflow by SHA, so they only get the fix after bumping that pin (#595).

Added

  • mecmcp-http: opt-in explicit egress proxy, HttpClientConfig::explicit_proxy: Option<ProxyUrl> (#589). None, the default, is unchanged: no proxy. ProxyUrl::parse accepts only an http:// or https:// URL with a host, no path, query, or fragment, and at most 2048 bytes serialized (hyper-util would otherwise drop an over-long proxy without an error and go direct); HTTPS origins are tunnelled with CONNECT, so TLS stays end-to-end. Userinfo is accepted and sent as Proxy-Authorization: Basic, matching rustsdcmcp's egress_proxy. It never appears in Debug or errors, and ProxyUrl has no Display. Environment proxy variables (HTTP(S)_PROXY, ALL_PROXY, NO_PROXY) stay ignored with or without it.

Changed

  • Breaking for source (#589): mecmcp_http::HttpClientConfig has a new public field, explicit_proxy: Option<ProxyUrl>. Code that builds an HttpClientConfig by full struct literal must add explicit_proxy: None. rustmistmcp does (crates/rustmistmcp-core/src/client.rs:187 and :290) and will not compile until it does. Consumers that fill the rest with ..Default::default() — mecfeedmcp, rustopnsmcp, rustunifimcp, rustproxmoxmcp and mecviz — are unaffected. When rustsdcmcp moves its egress_proxy onto ProxyUrl, a deployed value with a path or query (which it accepts today and reqwest ignores) will be refused at startup.

v0.31.1

Fixed

  • mecmcp-redact: junos::redact_json_value now masks privacy-key, the one Junos-only REDACT_LOG_KEYS name the generic denylist missed, so get_junos_config format=json no longer returns it in plaintext (#591). Bare generic words in REDACT_LOG_KEYS (e.g. value) are deliberately not treated as secret JSON keys: they are ordinary field names in consumers' structured output.
  • mecmcp-redact: junos::redact_json_value string values now also get the Junos log vocabulary (redact_log_text), so raw CLI/config text in a field such as value is masked like junos::redact_text (#591).
  • mecmcp-redact: a junos::redact_json_value string value that starts with < and parses as XML (e.g. | display xml output in a batch commands[].value) gets the structural junos::redact_xml, so it stays well-formed. Other strings, including <-led text that does not parse, keep the text scan (#591).

... (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
  • 39e7308 release: v0.32.0 (#602)
  • 099fae4 feat(http): opt-in explicit egress proxy, still no autodiscovery (#589) (#601)
  • f86e978 fix(ci): retry cosign verify in reusable-release-image for registry lag (#595...
  • 4eafc30 build(deps): bump russh from 0.64.1 to 0.65.0 (#593)
  • 7c95948 docs(readme): rustjunosmcp v2.5.0 (#599)
  • b981a38 build(deps): bump docker/login-action (#590)
  • 4c9bc9c build(deps): bump the cargo-minor-patch group across 1 directory with 5 updat...
  • 1c99a9d release: v0.31.1 (#597)
  • dce7227 fix(redact): Junos JSON and XML redaction cover Junos-only keys and CLI text ...
  • ad48ce2 docs(readme): rustsdcmcp v0.6.0 (#596)
  • Additional commits viewable in compare view

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

Release notes

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

v0.32.0

Fixed

  • ci: reusable-release-image.yml Verify signatures (hard gate) now retries each ref's cosign verify (6 attempts, backoff 2/4/8/15/30 s, about 59 s) before failing. Docker Hub's referrers index is eventually consistent, so verify right after signing could report no signatures found and fail the release (seen on rustsdcmcp v0.6.0). The gate stays hard: a signature that never appears still fails the job with cosign's last error. Consumers pin this workflow by SHA, so they only get the fix after bumping that pin (#595).

Added

  • mecmcp-http: opt-in explicit egress proxy, HttpClientConfig::explicit_proxy: Option<ProxyUrl> (#589). None, the default, is unchanged: no proxy. ProxyUrl::parse accepts only an http:// or https:// URL with a host, no path, query, or fragment, and at most 2048 bytes serialized (hyper-util would otherwise drop an over-long proxy without an error and go direct); HTTPS origins are tunnelled with CONNECT, so TLS stays end-to-end. Userinfo is accepted and sent as Proxy-Authorization: Basic, matching rustsdcmcp's egress_proxy. It never appears in Debug or errors, and ProxyUrl has no Display. Environment proxy variables (HTTP(S)_PROXY, ALL_PROXY, NO_PROXY) stay ignored with or without it.

Changed

  • Breaking for source (#589): mecmcp_http::HttpClientConfig has a new public field, explicit_proxy: Option<ProxyUrl>. Code that builds an HttpClientConfig by full struct literal must add explicit_proxy: None. rustmistmcp does (crates/rustmistmcp-core/src/client.rs:187 and :290) and will not compile until it does. Consumers that fill the rest with ..Default::default() — mecfeedmcp, rustopnsmcp, rustunifimcp, rustproxmoxmcp and mecviz — are unaffected. When rustsdcmcp moves its egress_proxy onto ProxyUrl, a deployed value with a path or query (which it accepts today and reqwest ignores) will be refused at startup.

v0.31.1

Fixed

  • mecmcp-redact: junos::redact_json_value now masks privacy-key, the one Junos-only REDACT_LOG_KEYS name the generic denylist missed, so get_junos_config format=json no longer returns it in plaintext (#591). Bare generic words in REDACT_LOG_KEYS (e.g. value) are deliberately not treated as secret JSON keys: they are ordinary field names in consumers' structured output.
  • mecmcp-redact: junos::redact_json_value string values now also get the Junos log vocabulary (redact_log_text), so raw CLI/config text in a field such as value is masked like junos::redact_text (#591).
  • mecmcp-redact: a junos::redact_json_value string value that starts with < and parses as XML (e.g. | display xml output in a batch commands[].value) gets the structural junos::redact_xml, so it stays well-formed. Other strings, including <-led text that does not parse, keep the text scan (#591).

... (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
  • 39e7308 release: v0.32.0 (#602)
  • 099fae4 feat(http): opt-in explicit egress proxy, still no autodiscovery (#589) (#601)
  • f86e978 fix(ci): retry cosign verify in reusable-release-image for registry lag (#595...
  • 4eafc30 build(deps): bump russh from 0.64.1 to 0.65.0 (#593)
  • 7c95948 docs(readme): rustjunosmcp v2.5.0 (#599)
  • b981a38 build(deps): bump docker/login-action (#590)
  • 4c9bc9c build(deps): bump the cargo-minor-patch group across 1 directory with 5 updat...
  • 1c99a9d release: v0.31.1 (#597)
  • dce7227 fix(redact): Junos JSON and XML redaction cover Junos-only keys and CLI text ...
  • ad48ce2 docs(readme): rustsdcmcp v0.6.0 (#596)
  • Additional commits viewable in compare view

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

Release notes

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

v0.32.0

Fixed

  • ci: reusable-release-image.yml Verify signatures (hard gate) now retries each ref's cosign verify (6 attempts, backoff 2/4/8/15/30 s, about 59 s) before failing. Docker Hub's referrers index is eventually consistent, so verify right after signing could report no signatures found and fail the release (seen on rustsdcmcp v0.6.0). The gate stays hard: a signature that never appears still fails the job with cosign's last error. Consumers pin this workflow by SHA, so they only get the fix after bumping that pin (#595).

Added

  • mecmcp-http: opt-in explicit egress proxy, HttpClientConfig::explicit_proxy: Option<ProxyUrl> (#589). None, the default, is unchanged: no proxy. ProxyUrl::parse accepts only an http:// or https:// URL with a host, no path, query, or fragment, and at most 2048 bytes serialized (hyper-util would otherwise drop an over-long proxy without an error and go direct); HTTPS origins are tunnelled with CONNECT, so TLS stays end-to-end. Userinfo is accepted and sent as Proxy-Authorization: Basic, matching rustsdcmcp's egress_proxy. It never appears in Debug or errors, and ProxyUrl has no Display. Environment proxy variables (HTTP(S)_PROXY, ALL_PROXY, NO_PROXY) stay ignored with or without it.

Changed

  • Breaking for source (#589): mecmcp_http::HttpClientConfig has a new public field, explicit_proxy: Option<ProxyUrl>. Code that builds an HttpClientConfig by full struct literal must add explicit_proxy: None. rustmistmcp does (crates/rustmistmcp-core/src/client.rs:187 and :290) and will not compile until it does. Consumers that fill the rest with ..Default::default() — mecfeedmcp, rustopnsmcp, rustunifimcp, rustproxmoxmcp and mecviz — are unaffected. When rustsdcmcp moves its egress_proxy onto ProxyUrl, a deployed value with a path or query (which it accepts today and reqwest ignores) will be refused at startup.

v0.31.1

Fixed

  • mecmcp-redact: junos::redact_json_value now masks privacy-key, the one Junos-only REDACT_LOG_KEYS name the generic denylist missed, so get_junos_config format=json no longer returns it in plaintext (#591). Bare generic words in REDACT_LOG_KEYS (e.g. value) are deliberately not treated as secret JSON keys: they are ordinary field names in consumers' structured output.
  • mecmcp-redact: junos::redact_json_value string values now also get the Junos log vocabulary (redact_log_text), so raw CLI/config text in a field such as value is masked like junos::redact_text (#591).
  • mecmcp-redact: a junos::redact_json_value string value that starts with < and parses as XML (e.g. | display xml output in a batch commands[].value) gets the structural junos::redact_xml, so it stays well-formed. Other strings, including <-led text that does not parse, keep the text scan (#591).

... (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
  • 39e7308 release: v0.32.0 (#602)
  • 099fae4 feat(http): opt-in explicit egress proxy, still no autodiscovery (#589) (#601)
  • f86e978 fix(ci): retry cosign verify in reusable-release-image for registry lag (#595...
  • 4eafc30 build(deps): bump russh from 0.64.1 to 0.65.0 (#593)
  • 7c95948 docs(readme): rustjunosmcp v2.5.0 (#599)
  • b981a38 build(deps): bump docker/login-action (#590)
  • 4c9bc9c build(deps): bump the cargo-minor-patch group across 1 directory with 5 updat...
  • 1c99a9d release: v0.31.1 (#597)
  • dce7227 fix(redact): Junos JSON and XML redaction cover Junos-only keys and CLI text ...
  • ad48ce2 docs(readme): rustsdcmcp v0.6.0 (#596)
  • Additional commits viewable 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

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


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

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

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

---
updated-dependencies:
- dependency-name: mechubsec/mecmcp/packaging/conformance
  dependency-version: 0.32.0
  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.32.0
  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.32.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  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 13, 2026
@fastrevmd-lab
fastrevmd-lab merged commit 35ee0e3 into main Nov 14, 2026
11 checks passed
@fastrevmd-lab
fastrevmd-lab deleted the dependabot/github_actions/github_actions-minor-patch-1a25eeab44 branch November 14, 2026 01:23
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