Repository navigation
Version Packages - #451
Merged
Merged
Version Packages#451
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
October 19, 2026 11:56
23c8c00 to
10439bc
Compare
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
Contributor
Author
|
Vercel previews (commit
|
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@cofhe/abi@1.0.1
Patch Changes
@cofhe/foundry-plugin@1.0.1
Patch Changes
@cofhe/hardhat-3-plugin@1.0.1
Patch Changes
@cofhe/hardhat-plugin@1.0.1
Patch Changes
@cofhe/react@1.0.1
Patch Changes
@cofhe/sdk@1.0.1
Patch Changes
fcc819c: Breaking:
encryptInputs(...).execute()now binds the consuming contract into the ZK proof itself, and the CoFHE verifier requires it. Upgrade to 1.0.1: 1.0.0 is deprecated because of an issue in ZK verification, and once the verifier is updated a proof from 1.0.0 fails withZK_VERIFY_FAILED. No code change is needed beyond the upgrade;setConsumingContract(...)was already required.execute()now throwsCofheErrorwith codeCONSUMING_CONTRACT_INVALIDwhensetConsumingContract(...)was given something that is not an address, before TFHE is initialised or any proving starts. The check is byte-level, 20 bytes of hex in any case, and does not validate the EIP-55 checksum, so every address 1.0.0 accepted still passes. Previously the bad address reached the verifier and failed there, after the proof was generated.CofheErrorCodegainsConsumingContractInvalid; an exhaustiveswitchover the enum needs the new arm.@cofhe/mock-contracts@1.0.1
@cofhe/example-react@1.0.1
Patch Changes
@cofhe/site@1.0.1