Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/workflows/lsp.yml
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,9 @@ jobs:
github-token: ${{ github.token }}
targets: ${{ matrix.settings.target }}

- name: Setup Zig
uses: ./.github/actions/setup-zig

- name: Build Setup
shell: bash
if: ${{ matrix.settings.setup }}
Expand Down
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,4 +63,4 @@ docs: Update installation instructions
- Canary VS Code extension packages use `--pre-release`.
- Non-dry-run releases publish the VS Code extension through the `LSP` workflow using `publish=true`, `dry_run=false`, and a `VSCE_PAT` secret on the protected `vscode-marketplace` environment. This publish path must not block release PR creation or cleanup published npm release state.
- The `Release` workflow signs and notarizes macOS `turbo` binaries during `build-rust` using static GitHub secrets and `apple-codesign`/`rcodesign`.
- The `Release` workflow installs Zig during `build-rust` because `turbo` links vendored `libghostty-vt` through `turborepo-ghostty-sys`.
- The `Release` and `LSP` workflows install Zig during `build-rust` because `turbo` and `turborepo-lsp` link vendored `libghostty-vt` through `turborepo-ghostty-sys`.
Loading