|
5 | 5 | # Setup Typst |
6 | 6 |
|
7 | 7 | This action provides the following functionality for GitHub Actions users: |
| 8 | + |
8 | 9 | - **Installing** a version of [Typst] and adding it to the PATH |
9 | 10 | - **Caching** [packages] dependencies |
10 | 11 | - **Downloading** ZIP archives as packages |
|
62 | 63 | - run: typst-latest compile paper.typ paper.pdf |
63 | 64 | ``` |
64 | 65 |
|
| 66 | +> [!TIP] |
| 67 | +> |
| 68 | +> - `executable-name` defaults to `typst`. |
| 69 | +> - A Typst executable named `typst-${version}` is always kept. |
| 70 | +> - For Windows, there is no need to include the executable file extension `.exe` in the parameters. |
| 71 | +> - Multiple distinct `executable-name` values can be set for the same Typst version. Setting the same `executable-name` (including the default `typst`) for different Typst versions is **not recommended**, as it may lead to version management confusion. |
| 72 | + |
65 | 73 | #### Managing Packages with Cache |
66 | 74 |
|
67 | 75 | **`cache-dependency-path`:** Used to specify the path to a Typst file containing lines of `import` keyword. |
|
70 | 78 | # Example workflow YAML file |
71 | 79 | - uses: typst-community/setup-typst@v4 |
72 | 80 | with: |
73 | | - cache-dependency-path: requirements.typ |
| 81 | + cache-dependency-path: requirements.typ |
74 | 82 | ``` |
75 | 83 |
|
76 | 84 | ```typst |
@@ -104,6 +112,7 @@ jobs: |
104 | 112 | ``` |
105 | 113 |
|
106 | 114 | > [!TIP] |
| 115 | +> |
107 | 116 | > - For links to download GitHub repositories, please refer to [_Downloading source code archives_]. |
108 | 117 | > - The supported namespaces are only `local` and `preview`. |
109 | 118 | > - The SemVer versions of packages are read from its `typst.toml`. |
@@ -166,6 +175,7 @@ You can also use `npm run lint` to run type checking and format code with `npm r |
166 | 175 | The repository uses GitHub Actions for continuous integration testing. The workflow automatically runs on pull requests and pushes to the main branch. |
167 | 176 |
|
168 | 177 | The CI workflow consists of two kinds of jobs: |
| 178 | + |
169 | 179 | - Build: Compiles the action and uploads artifacts |
170 | 180 | - Test: Tests the action across all platforms |
171 | 181 | - Basic Test: Tests basic functionality |
|
0 commit comments