ci(release): trigger update-image-tag + drop npm publishing#114
Merged
Conversation
Add an `update` job to release.yml that dispatches the local update-image-tag.yaml workflow once the multi-arch images are published, mirroring the `update` job in morpho-org/morpho-api (push.yml): github-script + createWorkflowDispatch via the workflow GITHUB_TOKEN (actions: write). It depends only on docker-manifest, so a failing GoReleaser/npm `release` job never blocks deployment. The release_url is derived from the tag that triggered the workflow, not from the release job.
0x666c6f
approved these changes
Jul 10, 2026
rguichard
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two release-workflow adjustments for the
morpho-org/erpcfork:update-image-tagafter a successful Docker push — a new release now automatically opens the chart image-tag bump PR.Changes
1. New
updatejob (dispatchupdate-image-tag.yaml)needs: [docker-manifest]andif: push && tag— runs only after a successful Docker build+push. It does not depend on the GoReleaserreleasejob.update-image-tag.yaml(onmorpho-main) viaactions/github-script@v7+github.rest.actions.createWorkflowDispatch, using the workflowGITHUB_TOKENwithpermissions: { actions: write, contents: read }(workflow_dispatchis the documented exception that letsGITHUB_TOKENstart another workflow — no App token needed).version_tag(validated semver from the release tag) andrelease_urlderived from the triggering release tag, not from thereleasejob.updatejob inmorpho-org/morpho-api(.github/workflows/push.yml) for long-term maintainability.2. Remove npm publishing
morpho-org/erpcis a fork oferpc/erpcand does not own@erpc-cloud/cli,erpc,start-rpc,start-erpc,@erpc-cloud/config(npm returns E404 on PUT for unauthorized publishes; noNPM_TOKENis configured either).releasejob..github/scripts/publish-npm.sh.Testing
release.ymlvalidated as well-formed YAML.updatejob already ran green on release0.1.6(run 29079819595) and dispatchedupdate-image-tag.yaml; that same run's failure was the npm publish step this PR removes.Notes
prepare-releasejob (workflow_dispatch path) still bumpspackage.jsonversions and generates CLI release files. It doesn't publish, so it doesn't fail — left as-is. Can be trimmed in a follow-up if the fork wants npm gone entirely.