[TECHOPS-1244] Drop the dry-run ECR claim from the workflows README - #8009
sayaliM0412 wants to merge 1 commit into
Conversation
The README said a dryRun release ends with a docker image in 812559712860.dkr.ecr.us-east-1.amazonaws.com/liquibase-dry-run. Neither half of that is true any more: release-published-orchestrator.yml skips docker-release.yml on a dryRun, and build-logic's reusable-docker-build.yml no longer pushes anywhere on a dry run. The ecr.png screenshot went with the sentence that referenced it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe workflow README updates the dryRun release documentation. It states that Docker images are not published, describes the relevant workflow behavior, and removes the obsolete ECR image reference. ChangesDry-run release documentation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This documentation-only change does not alter workflow behavior and presents no actionable merge risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔎 What
Removes the sentence (and its screenshot) claiming a dryRun release ends with a docker image in
812559712860.dkr.ecr.us-east-1.amazonaws.com/liquibase-dry-run.🧨 Why
Neither half of that sentence is true any more:
release-published-orchestrator.ymlskipsdocker-release.ymlentirely on a dryRun (inputs.dry_run != true), becausedocker-release.ymlresolves the SHA256 frompackage.liquibase.com, which only hosts GA tarballs.docker-release.ymlrun dispatched by hand withdryRun: trueused to push to that private ECR repo throughbuild-logic'sreusable-docker-build.yml. feat(docker): stop pushing dry-run images to private ECR (TECHOPS-1244) build-logic#707 changes a dry run to build every platform and push to no registry, because nothing in any Liquibase repo ever pulled fromliquibase-dry-run, while Inspector kept rescanning the 1,341 images it had accumulated since 2024-08-27.✅ Verification
grepacross liquibase, liquibase-pro, docker, build-logic and liquibase-infrastructure: no workflow, script or QA job pulls fromliquibase-dry-run.📦 Scope
Docs only: one sentence in
.github/workflows/README.mdand the now-unreferenceddoc/img/ecr.png. No workflow behaviour changes in this repo.🤖 Generated with Claude Code