Repository navigation
chore: scaffold templates v0.21.1 - #330
Merged
Merged
Conversation
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
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.
Pins
SEAMLESS_TEMPLATES_REFto v0.21.1 (501479f). That release runs the production web and Next.js images as non-root on port 8080 (seamless-templates#142), which the compose file from #326 already maps. Until this lands,seamless initon main maps 5173 to 8080 on v0.21.0 images that listen on 80, so release the CLI only after this merges.Checks:
npm run build: oknpm run check:templates-pin:SEAMLESS_TEMPLATES_COMMIT matches fells-code/seamless-templates v0.21.1 (501479f260225c56122b2bc1dfb7c1304efed08f), other four pins matchnpm test: 1548 passed, 4 skipped