Repository navigation
Conversation
前两次 Version & Release 均失败于 GH013：main 的 ruleset 强制 "Changes must be made through a pull request"，把 semantic-release 自身的发版推送（chore(release) 提交 + CHANGELOG + tag → HEAD:main） 一并拦截。 修复：checkout 与 semantic-release 环境改用 secrets.RELEASE_TOKEN （细粒度 PAT，Contents:RW，持有者为仓库 admin），配合 ruleset Bypass list（Repository admin）实现发版链路的受控绕过； 未配置该 secret 时回退内置 token，行为与现状一致（不劣化）。 需要仓库侧配套（手工步骤）： 1) 创建细粒度 PAT（仅 Entropydecrease 仓库，Contents: Read and write） 2) 仓库 Settings → Secrets → Actions 新建 RELEASE_TOKEN 3) main-protection ruleset → Bypass list 添加 Repository admin
Owner
Author
|
🎉 This PR is included in version 0.25.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Aparencia
added a commit
that referenced
this pull request
Aug 4, 2026
- #1: JWT algorithm now injected via SUPABASE_JWT_ALGORITHM (default HS256, aligned with Supabase default signing); placeholder detection prevents 'configured' false impression causing whole-site 401 - #2: remove double rollback on streaming rate-limit overrun - the Lua script already atomically DECRs, manual rollback let users drain their own quotas into negative counts - #3: error_pattern chain/router defensive validation - missing fields from LLM JSON output filtered instead of 500 (ValidationError) - #4: GLM generate_vision returns actual clamped max_tokens; vision chain logs truncation warning when output approaches the limit
Aparencia
added a commit
that referenced
this pull request
Sep 13, 2026
批 8 T16（欠账 #3 + 控制方新增的 T13 实测两条）。 - app/src/utils/markdownLine.ts（100 → 106）：① 更正头部边界段的档位名 —— 配图行 -  落 li 档而非段落档（T13 实测 + 本单元 esbuild 复现，逐字 <div style="font-size:12px;color:#4b5563">• </div>）；② 登记 T13 的另一条 发现：工作台链（utils/refineDiff.ts）没有 NotePreviewView.tsx:52-67 那道配图拦截 ⇒ 配图行在工作台渲染成字面文本（只登记、不改行为）；③ 登记 6 个原始 hex（utils/** 不在 零颜色字面量守卫域，style-seams.test.ts:248）⇒ 只登记、不改值。
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.
概要
修复 Version & Release 工作流两次失败（GH013）的发版链路：semantic-release 的发版推送改用
RELEASE_TOKEN（细粒度 PAT）+ ruleset Bypass（Repository admin），实现受控绕过 main 的 PR 强制规则。变更内容
.github/workflows/version-release.ymltoken改为secrets.RELEASE_TOKEN || github.tokenGITHUB_TOKEN改为secrets.RELEASE_TOKEN || secrets.GITHUB_TOKEN根因
main 的 ruleset 强制 "Changes must be made through a pull request"，把 semantic-release 自身的发版推送（
chore(release)提交 + CHANGELOG + tag →HEAD:main）一并拦截：配套（已完成的仓库侧手工配置）
RELEASE_TOKEN验证
合并本 PR 后 Version & Release 应成功产出 v0.25.0（CHANGELOG + tag + GitHub Release）。