Repository navigation
feat(azure-host): publish the host's image to ghcr.io on release - #327
Merged
Merged
Conversation
smith 1.13.0 prunes a Node app (monosmith-app/monosmith#297), so the docker convention is back on: azure-host's prune task writes dist/ with its own package.json, lockfile and the workspace packages it uses, PRs build the image without pushing, and each release pushes it as ghcr.io/open-craw/opencraw-azure-host. The docs run smith's prune instead of Nx's. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01TjR6eM2tUwU3NGnKXsmEap
Release preview
Unchanged: agent, office-reader, core, probe, studio, cli, mcp, azure-durable, captcha-tesseract, driver, ocr-tesseract, opencraw |
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.
smith 1.13.0 ships a Node app prune (monosmith-app/monosmith#297), so the docker convention is back on (it was turned off in #319).
[conventions.docker]:registry = "ghcr.io/open-craw". Each release pushesghcr.io/open-craw/opencraw-azure-hostwith the workflow'sGITHUB_TOKEN;ci.ymlgainspackages: write. PRs build the image without pushing.[projects.azure-host.docker]:context = "apps/azure-host", where the Dockerfile readsdist/.prune:smith npm-prune apps/azure-host --out apps/azure-host/dist. It writes the app's ownpackage.json, a lockfile cut from the workspace's, and the 8@opencrawpackages it uses underdist/workspace_modules. That is exactly what the Dockerfile copies.deploy.shanddocs/recipes/azure-durable.mdnow saysmith run prune -p azure-hostinstead of the Nx target.Verified locally:
smith run prune -p azure-host: 18 of 18 tasks succeeded.smith run lint typecheck test build: 76 of 76.npm run lint:workspace: passes.smith doctor: 52 passed. Its one failure is this machine's Docker engine not running.Not verified locally:
docker builditself, for the same reason. This PR's CI is the image's first real build.deploy.shstill builds its own image in ACR. Pointing it at the ghcr image follows once the first release has pushed one.🤖 Generated with Claude Code
https://claude.ai/code/session_01TjR6eM2tUwU3NGnKXsmEap