Conversation
The release.published event from changesets/action (using GITHUB_TOKEN) does not trigger other workflows due to GitHub Actions limitations. Add workflow_dispatch as a manual trigger with version input. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9832f17b67
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| TAG="${{ github.event.release.tag_name }}" | ||
| VERSION="${TAG#@transloadit/mcp-server@}" | ||
| if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then | ||
| VERSION="${{ github.event.inputs.version }}" |
There was a problem hiding this comment.
Bind manual image tag to the code ref being built
For workflow_dispatch, the version is taken verbatim from ${{ github.event.inputs.version }} here, but the job still builds whatever ref was dispatched (typically main via actions/checkout@v4). That means triggering this workflow after main has advanced (or entering an older version) can publish a mismatched image under that semver tag (and latest), which can ship incorrect code to users. The manual path should derive the tag from the checked-out source or explicitly check out the release tag that matches the requested version.
Useful? React with 👍 / 👎.
Summary
workflow_dispatchtrigger withversioninput to the Docker MCP workflowrelease.publishedevent fromchangesets/action(usingGITHUB_TOKEN) doesn't trigger other workflows due to GitHub Actions limitationsTest
After merging, run manually: Actions > Docker MCP Server > Run workflow > version: 0.3.8
🤖 Generated with Claude Code