feat(release): stop building the engine Docker image — engine is lib-only#38
Merged
Conversation
…only The engine image's only consumer was pineforge-release; everything else (codegen, Pine entrypoint, standalone use) moved to the hub, and C-ABI linkers use the prebuilt tarballs. So drop the Docker build/push from release.yml and delete docker/Dockerfile. The engine now ships as a C++ library: source + per-arch GitHub Release tarballs (libpineforge.a + headers). pineforge-release builds its combined image FROM that tarball. The hub dispatch moves to a new notify-hub job (needs: [release, prebuilt]) so it fires only AFTER the tarballs are uploaded (the hub builds from them). Release notes point users to ghcr.io/.../pineforge-release for the full image. docker/entrypoint.sh + run_json.py stay (tested by ctest; hub ships its own copy). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
The engine image's only consumer was pineforge-release; everything else (codegen,
Pine entrypoint, standalone use) moved to the hub, and C-ABI linkers use the
prebuilt tarballs. So drop the Docker build/push from release.yml and delete
docker/Dockerfile. The engine now ships as a C++ library: source + per-arch
GitHub Release tarballs (libpineforge.a + headers). pineforge-release builds its
combined image FROM that tarball.
The hub dispatch moves to a new notify-hub job (needs: [release, prebuilt]) so it
fires only AFTER the tarballs are uploaded (the hub builds from them). Release
notes point users to ghcr.io/.../pineforge-release for the full image.
docker/entrypoint.sh + run_json.py stay (tested by ctest; hub ships its own copy).
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com