Repository navigation
更新 Magpie 界面并加固认证、上传和数据恢复 - #2
Merged
Merged
Conversation
added 2 commits
September 27, 2026 18:25
Enforce file, share, version and session authorization; isolate untrusted render content and scope private bundle access. Validate uploads and restore archives, preserve token encryption keys, and roll back failed restores. Upgrade dependencies and supported Node runtimes, remove the vulnerable development watcher, and add security regressions and deployment guidance. Validation: 406 tests passed on Node 22 and Node 24; lint and build passed; full and production dependency audits report zero known vulnerabilities; isolated HTTPS acceptance passed.
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.
将已确认的 Magpie 界面更新与安全修复合入 main：更新工作台界面，补齐文件、分享、版本和会话权限；隔离用户内容，校验 ZIP 上传与备份恢复，升级依赖与支持的 Node 版本，并加入安全回归测试和部署说明。
验证：提交 67ee6f2 的 GitHub CI 已通过，Node 22、24 下的全部依赖安全扫描、代码检查、单元及集成测试、前端构建均成功。本地隔离 HTTPS 验收也已通过。实际生产平台部署验收仍需在目标环境执行。