feat(ci): add express-only option to npmjs-release workflow#8648
Open
bitgo-ai-agent-dev[bot] wants to merge 1 commit intomasterfrom
Open
feat(ci): add express-only option to npmjs-release workflow#8648bitgo-ai-agent-dev[bot] wants to merge 1 commit intomasterfrom
bitgo-ai-agent-dev[bot] wants to merge 1 commit intomasterfrom
Conversation
Adds an `express-only` boolean input to the `npmjs-release` workflow dispatch. When set to `true`, the `get-release-context` and `release-bitgojs` jobs are skipped and only `get-express-release-context` and `publish-express-to-docker-hub` run. This allows the express Docker image to be re-published independently after a partial release failure where the npm packages were already published successfully. Ticket: WCN-308
bitgo-ai-agent-dev
Bot
requested review from
kisslove-dewangan and
mohammadalfaiyazbitgo
bitgo-ai-agent-dev
Bot
force-pushed
the
wcn-308-express-only-release
branch
from
ffc9757 to
41c2a87
Compare
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
1 participant
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
express-onlyboolean input (defaultfalse) to thenpmjs-releaseworkflow dispatchexpress-only: true, theget-release-contextandrelease-bitgojsjobs are skipped viaif: inputs.express-only == falseget-express-release-contextruns when eitherexpress-onlyis set orrelease-bitgojssucceeded:inputs.express-only == true || needs.release-bitgojs.result == 'success'publish-express-to-docker-hubis unmodified — it depends only onget-express-release-contextas beforeUse case
During release recovery after a partial publish failure where npm packages were already published, operators can re-trigger the workflow with
express-only: trueto rebuild and push the Express Docker image without re-running the lerna publish step.Test plan
express-only: false(default) — full pipeline runs as beforeexpress-only: true—get-release-contextandrelease-bitgojsjobs are skipped;get-express-release-contextandpublish-express-to-docker-hubrun against the existingrel/latesttagTicket: WCN-308
🤖 Generated with Claude Code