Skip to content

fix: turn azure-host's image release off until the image builds in CI - #319

Merged
russoedu merged 1 commit into
mainfrom
fix/azure-host-image-push
Oct 17, 2026
Merged

russoedu merged 1 commit into
mainfrom
fix/azure-host-image-push

Conversation

@russoedu

Copy link
Copy Markdown
Collaborator

Main's release after #318 failed at docker build for azure-host. Nothing was tagged or pushed (no azure-host tag, no GitHub Release, no ghcr package). There are two causes: the Dockerfile installs from a pruned dist/ (its own lockfile and the workspace packages it uses), which Nx's prune target wrote and smith doesn't yet; and smith builds from the workspace root. This turns [conventions.docker] off again, keeping the ghcr.io settings as a comment, so main's release passes. smith release --dry-run is back to "Nothing to release". The real fix is monosmith-app/monosmith#297.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TjR6eM2tUwU3NGnKXsmEap

The first release with the docker convention failed at docker build: the
Dockerfile installs from a pruned dist/ (its own lockfile and the
workspace packages it uses) that Nx's prune target wrote and smith does
not yet, and smith builds from the workspace root. Nothing was tagged or
pushed. The convention is off again, its ghcr.io settings kept as a
comment, so main's release passes (monosmith #297).

Refs #313

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TjR6eM2tUwU3NGnKXsmEap
@github-actions

Copy link
Copy Markdown

Release preview

Nothing to release.

Unchanged: agent, office-reader, core, probe, studio, cli, mcp, azure-durable, captcha-tesseract, ocr-tesseract, opencraw

@russoedu
russoedu merged commit 045a082 into main Oct 17, 2026
2 checks passed
@russoedu
russoedu deleted the fix/azure-host-image-push branch October 17, 2026 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant