Skip to content

CI: resolve the jolt release tag with the job token #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yogthos merged 1 commit into from
Sep 7, 2026
Merged

CI: resolve the jolt release tag with the job token #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 9 additions & 1 deletion .github/workflows/tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ jobs:
steps:
- uses: actions/checkout@v4
- name: Install jolt
env:
GH_TOKEN: ${{ github.token }}
run: |
set -euo pipefail
sudo apt-get update
Expand All @@ -20,8 +22,14 @@ jobs:
# release asset here: it owns the archive and binary naming (which
# changed in v0.5.0, when the CLI was renamed from joltc to jolt) and
# verifies the checksum. Hardcoding either broke this workflow once.
# The one thing resolved here is the release tag: left to the script,
# "latest" is an unauthenticated api.github.com call, and the quota
# for that is shared across every Actions runner on the same IP, so
# it answers 403 on a busy hour (the v0.0.9 tag run failed that way).
# gh makes the same call with the job's token.
tag="$(gh api repos/jolt-lang/jolt/releases/latest -q .tag_name)"
curl -fsSL https://raw.githubusercontent.com/jolt-lang/jolt/main/install \
| bash -s -- --dir "$HOME/.jolt"
| bash -s -- --dir "$HOME/.jolt" --version "$tag"
echo "$HOME/.jolt" >> "$GITHUB_PATH"
- name: Test
run: JOLT_PWD="$PWD" jolt -M:test
Loading