fix(release): split express context into get-express-release-context job#8611
Merged
Conversation
bitgo-ai-agent-dev
Bot
force-pushed
the
vl-4192-fix-express-docker-check
branch
2 times, most recently
from
d85e9e5 to
64e0c9f
Compare
louib
force-pushed
the
vl-4192-fix-express-docker-check
branch
from
64e0c9f to
e14f8c7
Compare
Extract express version/tag resolution and Docker Hub existence check
into a dedicated get-express-release-context job that runs after
release-bitgojs, so it evaluates the newly-published version rather
than the previously-released one.
Workflow chain: get-release-context → release-bitgojs
→ get-express-release-context → publish-express-to-docker-hub
Ticket: VL-4192
louib
force-pushed
the
vl-4192-fix-express-docker-check
branch
from
e14f8c7 to
c3edce2
Compare
mrdanish26
approved these changes
Apr 22, 2026
lokesh-bitgo
approved these changes
Apr 23, 2026
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
3 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
get-express-release-contextjob that runs afterrelease-bitgojs: reads the newly-bumped express version fromrel/latest, resolves the lerna git tag, sanity-checks the version bump, and checks whether the Docker image already existspublish-express-to-docker-hubnow depends only onget-express-release-contextand is skipped ifdocker-exists == trueget-release-contextentirelyget-release-context→release-bitgojs→get-express-release-context→publish-express-to-docker-hubTest plan
dry-run: true—get-express-release-contextandpublish-express-to-docker-hubshould be skippeddry-run: false— verify express context job reads the post-lerna version and publish job runsTicket: VL-4192