Add automated e-book release workflow - #74
Merged
Conversation
Publish BlimaCake.epub as a GitHub Release via .github/workflows/release.yml: triggered by pushing a cookbook-* tag or by manual workflow_dispatch with a tag input. The workflow rebuilds the EPUB from the current Markdown (deterministic build) and attaches it, so the released file always matches the recipes. Scoped contents: write; existing validation gates untouched. Documented in docs/about-this-archive.md. Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HpG2vky2XhDtfc6y16TRis
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
2 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.
Publishes the cookbook as a GitHub Release with
BlimaCake.epubattached, so the release step no longer needs a manual upload.What changed
.github/workflows/release.yml. Triggers on pushing a tag namedcookbook-*(for examplecookbook-2026-07) or from the Actions tab viaworkflow_dispatch(supply the tag). It rebuildsBlimaCake.epubfrom the current Markdown in the runner and attaches it to the release withsoftprops/action-gh-release@v2, so the released file always matches the recipes even if the committed root copy was not refreshed.docs/about-this-archive.md. Updated the maintainer note to describe the workflow instead of the manual Releases-page steps.Why a workflow (and not an MCP/API call)
GitHub uploads release binaries through a separate binary endpoint, which does not map onto the JSON-based GitHub tools this project uses, and the direct API/
ghpath is unavailable to the assistant here. Running the upload on a GitHub runner sidesteps both: the runner already has the file and the standard release action handles the binary upload.Safety
contents: writepermission (needed to create a release); nothing else is granted.requirements.txtprovides PyYAML + Pillow). Verified locally: the exact build command produces a structurally valid EPUB (mimetype first and STORED, container.xml and package.opf present, 487 recipes).🤖 Generated with Claude Code
https://claude.ai/code/session_01HpG2vky2XhDtfc6y16TRis
Generated by Claude Code