Repository navigation
fix: fail closed for native collection methods - #5
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks done
Cylop
force-pushed
the
fix/native-method-hardening
branch
from
September 4, 2026 11:16
6b0442d to
f1c8c23
Compare
This branch was successfully deployed
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
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
2.0.1; this PR does not publish it.Verification
npm run release:checknpm run test:browser— 22 passed locally (Chromium and Firefox; WebKit required in Linux CI)2.0.1remains unpublished and npmlatestremains2.0.0Membrane review
Release order
Merge this PR first. After green
mainCI and production deployment verification, publish the protected2.0.1release workflow. The product-story PR must not merge or deploy until npm verifies both exact2.0.1andlatest = 2.0.1.