fix: close verified input factory bypass - #10
Merged
Conversation
PureSaber
added a commit
that referenced
this pull request
Aug 31, 2026
fix: close verified input factory bypass
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
2 participants
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.
范围
VerifiedFactorInput模块级认证token和可直接调用的类工厂契约影响
puresaber.verified-factor-input@1.0.0序列化字段不变；Python对象构造方式收紧，消费者必须继续使用两个公开loader。测试证据
回滚
Git revert本PR的merge commit并恢复v0.8.0依赖；不移动或重建任何既有tag。