Skip to content

Warn when typst version inputs are ignored - #67

Merged
yusancky merged 1 commit into
typst-community:mainfrom
yusancky:main
May 30, 2026
Merged

Warn when typst version inputs are ignored#67
yusancky merged 1 commit into
typst-community:mainfrom
yusancky:main

Conversation

@yusancky

Copy link
Copy Markdown
Member

When typst-versions-* is provided, typst-version and executable-name are ignored today without any signal. This change makes that override explicit so users can see when their single-version inputs are being bypassed.

  • Input conflict warning

    • Emit a core.warning when typst-versions-* is set alongside non-default typst-version / executable-name inputs.
    • Keep the message consistent with existing warning style in the action.
  • Multiple typst-versions-* inputs warning

    • Emit a core.warning when more than one typst-versions-* input is set.
    • Clearly state which typst-versions-* input is used and which ones are ignored.
  • Preserve existing behavior

    • Multi-version installation still takes precedence.
    • Default single-version inputs remain unchanged when no typst-versions-* input is present.
with:
  typst-versions-file: config.json
  typst-version: v0.14
  executable-name: typst-latest

With this configuration, the action now warns that typst-version and executable-name are ignored.

When `typst-versions-*` is provided, `typst-version` and `executable-name` are ignored today without any signal. This change makes that override explicit so users can see when their single-version inputs are being bypassed.

- **Input conflict warning**
  - Emit a `core.warning` when `typst-versions-*` is set alongside non-default `typst-version` / `executable-name` inputs.
  - Keep the message consistent with existing warning style in the action.

- **Multiple `typst-versions-*` inputs warning**
  - Emit a `core.warning` when more than one `typst-versions-*` input is set.
  - Clearly state which `typst-versions-*` input is used and which ones are ignored.

- **Preserve existing behavior**
  - Multi-version installation still takes precedence.
  - Default single-version inputs remain unchanged when no `typst-versions-*` input is present.

```yaml
with:
  typst-versions-file: config.json
  typst-version: v0.14
  executable-name: typst-latest
```

With this configuration, the action now warns that `typst-version` and `executable-name` are ignored.
@yusancky
yusancky merged commit 25c4020 into typst-community:main May 30, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants