Pages workflow: do not let setup-typst pre-compile page.typ - #150
Merged
Merged
Conversation
setup-typst warms its package cache by compiling the file named in cache-dependency-path, without the --input values page.typ needs, so the deploy failed before the site build ran. The cmarker package is fetched by the first compile in build.py instead.
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 first Pages deploy after #149 failed in the setup-typst step: with
cache-dependency-path: site/page.typthe action compiles that file itself to warm its package cache, without the--inputvalues the page needs, and stops there (dictionary does not contain key "source"). Dropping the option lets the site build download the cmarker package on its first compile, which is what happens locally. No other change.