This repository was archived by the owner on Nov 2, 2026. It is now read-only.
Repository navigation
ci: skip type-checking on final publish (lib drift in frozen code) - #4
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
1.0.2failed on the merged release commit (run 41541057121):npx jsr publishtype-checks the package against the current TypeScript lib definitions and 3 pre-existing errors surface inform_data.ts/keystack.ts(SharedArrayBuffervsArrayBuffer,Uint8Array<ArrayBufferLike>vsBufferSource) — pure lib drift since 1.0.1 published; no package code changed.--no-checkto the publish step (the failure message's own hint). Fixing the type drift would be compatibility work for future toolchains, which is explicitly out of scope for a retired package. 1.0.2 contains no functional code changes relative to 1.0.1 — onlydeno.json's version and the README deprecation notice.