Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Improve registry release reliability#1174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
MattBabbage wants to merge1 commit intomain
base:main
Choose a base branch
Loading
frombabbage/link-registry-publish-to-docker-image

Conversation

MattBabbage
Copy link
Contributor

@MattBabbageMattBabbage commentedOct 3, 2025
edited
Loading

This pull request updates the release workflow to decouple Docker image publishing from MCP Registry publication, ensuring that registry updates only occur after a successful image build and push. The workflows now communicate via a custom GitHub repository dispatch event.

Changes

Registry should be released when docker image is created -> added trigger after docker image release
Registry pipeline should check if image is released and delay if now -> add check and delay

@MattBabbageMattBabbage requested a review froma team as acode ownerOctober 3, 2025 10:35
@CopilotCopilotAI review requested due to automatic review settingsOctober 3, 2025 10:35
Copilot

This comment was marked as resolved.

Copy link

@killers10killers10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Dvbbhhgf

Copy link

@killers10killers10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Evildead

build:
runs-on:ubuntu-latest-xl
permissions:
contents:read
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Do we need to change that to contents write?

Copy link
ContributorAuthor

@MattBabbageMattBabbageOct 6, 2025
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Only changes are local to 'server.json', nothing it written to repo so shouldn't require write permissions to repo itself

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@tonytrgtonytrgtonytrg left review comments

Copilot code reviewCopilotCopilot left review comments

+1 more reviewer

@killers10killers10killers10 requested changes

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@MattBabbage@tonytrg@killers10

[8]ページ先頭

©2009-2025 Movatter.jp