ci: remove the PDF documentation creation from the release workflow - #308
Merged
Conversation
Drop the "Create PDF" step (and its supporting "Setup node" step and the "Upload Document Artifacts" step) from the release automation. These converted README/CHANGELOG Markdown to PDF via md-to-pdf and uploaded them as a separate "documents" artifact, which no downstream job consumed (the platform-bundling jobs only pull `pattern: takajo-*`), so removing them does not affect the released binaries. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
YamatoSecurity
self-requested a review
July 11, 2026 02:09
YamatoSecurity
approved these changes
Jul 11, 2026
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.
Removes the PDF documentation generation from the release automation (
.github/workflows/release.yml).The
releasejob had threemacos-latest-gated steps dedicated to producing PDFs:md-to-pdf;npm i -g md-to-pdf+ convertingREADME*.md/CHANGELOG*.mdto PDF and renaming them per release version;./*.pdfas a separatedocumentsartifact.All three are removed. The
documentsartifact was not consumed by any downstream job —upload-all-platformsandall-packages-zipboth download withpattern: takajo-*— so this does not change the released binaries or the all-platforms/all-packages bundles.YAML validated; no lingering
pdf/md-to-pdf/documents/setup-nodereferences remain.