Release: Include template assets at their installation paths - #41
Merged
Conversation
whereareiam
added
bug
whereareiam
force-pushed
the
fix/package-template-styles
branch
from
September 5, 2026 20:39
2454a67 to
161f582
Compare
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 template archive omitted pull-commits.css and extracted scripts to assets/js instead of the documented public/assets/js installation path. Stage templates with their JavaScript and page-specific CSS under the correct custom-root paths before creating the archive.
Built all five release packs and verified that every custom stylesheet/script referenced by the templates exists at its installation path in the archive. Type checking and 350 tests passed before the independent CSS-budget fix; the combined release will be fully revalidated before publication.