Fix llms full txt artifact#49
Merged
Merged
Conversation
The fallback metadata source (used when the release-artifact download fails) only copied each npm package's meta/ directory — llms.txt ships at the package root, alongside meta/, so it was silently dropped there too. Verified against real npm packages (@helpers4/all, @helpers4/array) that llms.txt is genuinely present at that path in every package. Doesn't fix the currently-stale helpers4.dev/typescript/llms-full.txt on its own — that requires the release-artifact path (the one actually in use) to have llms.txt too, fixed separately in helpers4/typescript's release.yml. This just closes the same gap in the fallback path for defense-in-depth.
The 'Commit and push updated docs' step only staged
src/content/docs/${DOCS_TARGET}/ and src/data/versions.json —
generate-typescript-docs.js also writes public/typescript/llms-full.txt
(and its archived vN/ snapshots), but that path was never added. The
file could be correctly regenerated on disk with fresh content and the
step would still print 'No changes to commit' and exit, since nothing
under public/ was ever staged to diff against.
This is why re-triggering the workflow for v3.0.4 (after fixing the
build-meta.tar.gz artifact to include llms.txt) still didn't update the
live site: the generator logged '✓ published llms-full.txt', but the
commit step silently dropped it.
Verified end-to-end in a scratch worktree: ran the real generator
against the real (now-fixed) v3.0.4 build artifact, confirmed
public/typescript/llms-full.txt is the only file that changes (the
content pages were already up to date from earlier runs), and that the
old git add left it undetected while the fixed one stages and commits
it correctly.
Deploying helpers4 with
|
| Latest commit: |
7527414
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://62317509.helpers4.pages.dev |
| Branch Preview URL: | https://fix-llms-full-txt-artifact.helpers4.pages.dev |
✅ PR Validation Passed
📋 Pipeline Status
🤖 Generated by @helpers4 CI • 2026-07-21 |
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.
Description
Please include a summary of what this PR does and why it's needed.
Type of Change
Related Issues
Closes #(issue number)
How Has This Been Tested?
Describe the tests you ran and how to reproduce them:
Checklist
Screenshots (if applicable)
Add screenshots for UI changes.
Additional Context
Add any other context about the PR here.