Skip to content

chore: mark v0.0.72#1584

Merged
yury-s merged 1 commit intomicrosoft:mainfrom
yury-s:mark-v0.0.72
Apr 30, 2026
Merged

chore: mark v0.0.72#1584
yury-s merged 1 commit intomicrosoft:mainfrom
yury-s:mark-v0.0.72

Conversation

@yury-s
Copy link
Copy Markdown
Member

@yury-s yury-s commented Apr 30, 2026

Summary

  • Bumps @playwright/mcp to v0.0.72.

@yury-s yury-s merged commit 5ae9c9e into microsoft:main Apr 30, 2026
5 of 6 checks passed
yury-s added a commit that referenced this pull request May 1, 2026
#1586)

## Summary
- Expands the gate on `publish-mcp-release-registry` so it also runs on
`workflow_dispatch`. Lets us retroactively publish a previously-released
version (or rerun a failed publish) from the Actions tab without
re-running the npm release.
- Bumps `server.json` to `0.0.72` to match `package.json`. The
validation step added in #1585 would otherwise fail the next release,
since `mark v0.0.72` (#1584) landed before #1585 — `server.json` was
committed at `0.0.71`.

## Mechanics
The job still `needs: publish-mcp-release-npm` so on a real `release`
event it correctly waits for npm to publish first. On
`workflow_dispatch`, the npm job is skipped (its own `if` is
`release`-only), and `if: always() && needs.*.result !=
'failure'/'cancelled'` lets the registry job run anyway.

## Follow-up
Once merged, this enables a manual one-shot of v0.0.72 to the registry
via the Actions tab.

Follow-up to #1585.
Reference #1477
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.

2 participants