ci: pin Deno to last known-good 2.8.0 (2.9.5 segfaults at shutdown) - #47
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Flips the CI Deno pin from 2.9.5 → 2.8.0 (both
ci.ymlandpublish.yml). #44 pinned 2.9.5, but 2.9.5 is the version that segfaults: the crash started exactly when CI moved from the old.tool-versionspin (2.8.0) to floating/latest (which resolved to 2.9.5).Evidence (#41)
deno task ci(multiple)⇒ Linux-only native-binding teardown crash in Deno 2.9.5 ×
@libsql/client; not fixed by the client bump; all tests pass before the crash.2.8.0 is the last version with a green run on this repo and is the minimal-risk pin until the upstream incompatibility is understood. Follow-up issue for returning to latest-stable lands alongside this PR.