Skip to content

build(deps): bump ExaDev/mcp-registry-publish from 1.0.4 to 1.0.6 - #456

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/ExaDev/mcp-registry-publish-1.0.6
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/ExaDev/mcp-registry-publish-1.0.6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor

Bumps ExaDev/mcp-registry-publish from 1.0.4 to 1.0.6.

Release notes

Sourced from ExaDev/mcp-registry-publish's releases.

v1.0.6

1.0.6 (2026-10-22)

Full Changelog: ExaDev/mcp-registry-publish@v1.0.5...v1.0.6

v1.0.5

1.0.5 (2026-10-22)

Full Changelog: ExaDev/mcp-registry-publish@v1.0.4...v1.0.5

Changelog

Sourced from ExaDev/mcp-registry-publish's changelog.

1.0.6 (2026-10-22)

1.0.5 (2026-10-22)

1.0.4 (2026-10-22)

Bug Fixes

  • give the harness a union type for scripted version-check answers (90f94f3)
  • retry the registry version check on the publish retry budget (937fde9)

1.0.3 (2026-10-22)

Bug Fixes

  • log the registry's output with each retried failure (c5f0ab6)

1.0.2 (2026-10-22)

1.0.1 (2026-10-22)

1.0.0 (2026-10-22)

Features

  • classify the registry's publish failures that clear by themselves (27c6c61)
  • install a pinned, checksum-verified mcp-publisher (af9fea0)
  • publish a server.json with login and retry, as a library and a command (eeb2103)
  • run the publisher as a composite GitHub Action (4fff882)
  • skip a version the registry already lists (8d5f427)
Commits
  • d625f35 chore(release): 1.0.6 [skip ci]
  • 9d226ae chore: satisfy the padding rules in the tests
  • 5ac37be chore: satisfy the rules eslint-config 3 adds
  • 9aa59fd build(deps-dev): bump @​exadev/eslint-config from 2.20.1 to 3.1.0
  • a213446 chore(release): 1.0.5 [skip ci]
  • 9b88791 build(deps): bump actions/create-github-app-token from 3.2.0 to 3.3.0
  • 56d9bdf build(deps): bump actions/setup-node from 7.0.0 to 7.1.0
  • See full diff in compare view

Dependabot compatibility score

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


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [ExaDev/mcp-registry-publish](https://github.com/exadev/mcp-registry-publish) from 1.0.4 to 1.0.6.
- [Release notes](https://github.com/exadev/mcp-registry-publish/releases)
- [Changelog](https://github.com/ExaDev/mcp-registry-publish/blob/main/CHANGELOG.md)
- [Commits](ExaDev/mcp-registry-publish@4385896...d625f35)

---
updated-dependencies:
- dependency-name: ExaDev/mcp-registry-publish
  dependency-version: 1.0.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants