Skip to content

fix(ci): 放开 commitlint 行长限制修复发版自拦截 - #2

Merged
Aparencia merged 1 commit into
mainfrom
dev
Jul 30, 2026
Merged

Aparencia merged 1 commit into
mainfrom
dev

Conversation

@Aparencia

Copy link
Copy Markdown
Owner

v0.25.0 发版失败根因:semantic-release 的 chore(release) 提交 body 含 release notes 长 URL 行,被 body-max-line-length(100) 经 husky 拦截。禁用 body/footer 行长限制(header/type 校验保留)。已用实际失败信息验证 exit 0。仅改根配置文件,不触发部署工作流。

v0.25.0 发版失败根因:semantic-release 已完成版本计算与 CHANGELOG 生成,
但其自动创建的 chore(release) 提交 body 由 release notes 生成,天然含超长
commit URL 行,被我们刚启用的 commitlint body-max-line-length(100) 规则
经 husky commit-msg 钩子拦截(@semantic-release/git 插件执行 git commit 失败)。

处置:禁用 body-max-line-length 与 footer-max-line-length。该两条规则在
本仓库场景只会拦截合法提交(发布提交与人工贴链接),header 结构、type 枚举
等核心 Conventional Commits 校验全部保留。

验证:用实际失败的发版提交信息(含 140+ 字符 URL 行)过 commitlint,exit 0。
@Aparencia
Aparencia merged commit 05cdd0b into main Jul 30, 2026
5 checks passed
@Aparencia

Copy link
Copy Markdown
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 Jul 30, 2026
deploy-server / deploy-website 仅在 main 的 server/**、website/** 路径
变更时触发,且无手动入口——PR #2 修复后的新部署配置(scp 上传、
--env-file、真实服务器路径)至今从未实际执行过。

补 workflow_dispatch 后可手动触发做部署链路首跑验证,也可用于
紧急重部署(不依赖路径变更)。
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant