Skip to content

ci: pin deploy runner to ubuntu-24.04 - #1141

Merged
noblepayne merged 1 commit into
mainfrom
fix/pin-deploy-runner-2404
Oct 25, 2026
Merged

noblepayne merged 1 commit into
mainfrom
fix/pin-deploy-runner-2404

Conversation

@noblepayne

@noblepayne noblepayne commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

ubuntu-latest rolled to 26.04 on 2026-10-25. 26.04 ships sudo-rs, which silently ignores blanket sudo -E. The mechanism tailscale/github-action@v2 uses to carry TS_EXPERIMENT_OAUTH_AUTHKEY into tailscale up. The OAuth key is then rejected, Connect Tailscale exits 1, and the deploy never runs.

Pin to 24.04. Unpin once the action adopts sudo --preserve-env=TS_EXPERIMENT_OAUTH_AUTHKEY; v4.3.0 still uses -E.

Refs: sudo-rs#1299 · same breakage elsewhere

@noblepayne
noblepayne force-pushed the fix/pin-deploy-runner-2404 branch 2 times, most recently from 126a490 to c208947 Compare October 25, 2026 23:24
@noblepayne noblepayne changed the title ci: pin deploy runner to ubuntu-24.04 (26.04 sudo-rs drops -E) ci: pin deploy runner to ubuntu-24.04 Oct 25, 2026
As of 2026-10-25, ubuntu-latest is 26.04, which ships sudo-rs. sudo-rs
ignores the blanket `sudo -E` that tailscale/github-action relies on to
pass TS_EXPERIMENT_OAUTH_AUTHKEY into `tailscale up`, so Connect
Tailscale fails with "oauth authkeys are in experimental status" and the
deploy never runs. Failure: actions/runs/40243548131.

Interim. Unpin when the action uses
`sudo --preserve-env=TS_EXPERIMENT_OAUTH_AUTHKEY`; v4.3.0 still uses -E.

Refs: trifectatechfoundation/sudo-rs#1299
@noblepayne
noblepayne force-pushed the fix/pin-deploy-runner-2404 branch from c208947 to a065907 Compare October 25, 2026 23:25
@noblepayne
noblepayne merged commit 587112d into main Oct 25, 2026
1 check passed
@noblepayne
noblepayne deleted the fix/pin-deploy-runner-2404 branch October 25, 2026 23:26
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.

1 participant