project-release
Skill358 starsChanged 24 days agoMITView on GitHub
Release workflow for obsidian-wechat-converter (version bump, release notes, tag and publish).
- Commits and pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- ericwang200608-beep/LANYANT-Skillstheir own version, first seen Nov 8, 2026
- juanitourquiza/shipframetheir own version, first seen Oct 23, 2026
- NAVANEETHVVINOD/agent-orchestratortheir own version, first seen Oct 3, 2026
- kisev/skillstheir own version, first seen Sep 30, 2026
- salitaba/maven-decoder-mcptheir own version, first seen Sep 8, 2026
- breakstring/cfKanbantheir own version, first seen Sep 1, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- swimmwatch/cloakbrowser-mcp★ 172same name
- breakstring/cfKanban★ 28same name
- salitaba/maven-decoder-mcp★ 20same name
- juanitourquiza/shipframe★ 5same name
- ericwang200608-beep/LANYANT-Skills★ 2same name
- kisev/skills★ 2same name
- NAVANEETHVVINOD/agent-orchestrator★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- qiaomu-obsidian-devSkill
- wechat-ai-layoutSkill
The file
Files
Obsidian WeChat Converter Release Skill
发布新版本的完整流程。
版本号更新
发布新版本(如 2.5.6 -> 2.6.0)时,确保以下文件都已更新:
package.json: 更新"version": "..."manifest.json: 更新"version": "..."versions.json: 添加新版本映射,如"2.6.0": "0.15.0"README.md: 更新 Badge 中的版本号
提示:插件设置面板的「关于」页面(
views/settings/about-tab.js)会自动读取manifest.json中的version动态呈现标题版本号,无需手动修改代码。若本次发版包含新增赞助者,可顺带在services/sponsors-data.js中追加赞助鸣谢记录。
开发期门禁
在做 feature / enhancement 时,先跑快速自检:
npm run scan:guard它用于尽早发现新的 Obsidian scan 风险模式,但不替代最终发布前检查。
Release Notes
在 RELEASE_NOTES/ 目录下创建对应版本的文件:
RELEASE_NOTES/v{version}.md文件格式:
---
title: 简短标题(会显示为 "v{version} - 标题")
---
## 更新内容
### 🚀 重大更新
- ...
### 🐛 问题修复
- ...
### ✨ 功能优化
- ...发布流程
情况 A:当前在 feature 分支
- 准备阶段(在 feature 分支完成)
- 更新版本号文件
- 创建
RELEASE_NOTES/v{version}.md - 先运行
npm run scan:guard做快速自检 - 确保 Obsidian scan readiness guard 通过:
npm run review:guard
- 合并 PR
- 将 feature 分支合并到
main分支
- 将 feature 分支合并到
- 触发发布
git checkout main git pull git tag {version} git push origin {version}
情况 B:当前已在 main 分支
- 准备阶段
- 更新版本号文件
- 创建
RELEASE_NOTES/v{version}.md - 先运行
npm run scan:guard做快速自检 - 确保 Obsidian scan readiness guard 通过:
npm run review:guard
- 提交并触发发布
git add . git commit -m "chore: bump version to {version}" git push git tag {version} git push origin {version}
自动化流程
无论哪种情况,推送无前缀版本 tag 后 GitHub Actions 会自动执行:
- 校验
versions.json与manifest.json.minAppVersion映射 - 校验 tag 与
manifest.json.version一致,且不使用v前缀 - 运行
npm run review:guard,其中包含:- scan-risk guard
- ESLint
- 生产构建
- generated build artifact 一致性检查
- Vitest 全量测试
- release zip 打包
- release artifact 校验
- 创建 GitHub Release(从 release notes 文件读取内容)
- 上传 release 文件
- 同步安装资产到 Gitee Release(
main.js/manifest.json/styles.css,供国内无法访问 GitHub 的用户下载)
发版后验证 Gitee 镜像
GitHub Release 创建后,CI 会调用 Gitee OpenAPI 创建同名发行版并上传三个安装资产。 推送 tag 后约 1-2 分钟,用以下命令确认镜像侧产物齐全:
npm run release:verify-gitee <version>
# 例:npm run release:verify-gitee 2.12.1预期输出:
tag : 2.12.1
assets : styles.css, main.js, manifest.json, 2.12.1.zip, 2.12.1.tar.gz
✅ 三个安装资产齐全说明:
- Gitee 会自动为每个发行版生成
<tag>.zip/<tag>.tar.gz源码包,它们不算安装资产,无需理会。 - 校验失败(exit 1)时,先去 GitHub Actions 的
Sync release assets to Gitee步骤看日志; 该步骤配置了continue-on-error: true,即使失败也不会阻塞 GitHub 主发布流程。 - 若确认同步失败,可手动到 Gitee 发行版页补齐三个文件(从 GitHub Release 下载,SHA256 应与 GitHub 报告一致)。
- 未配置
GITEE_TOKENsecret 时,该同步步骤会打印 warning 并跳过,属预期行为。
Obsidian 社区插件注意事项
- Git tag 必须与
manifest.json.version完全一致,例如2.6.6 - 不要使用
v2.6.6这样的前缀 tag RELEASE_NOTES文件仍然沿用RELEASE_NOTES/v{version}.md- GitHub Release assets 需要至少包含:
main.jsmanifest.jsonstyles.css
- Gitee 镜像 Release 需包含完全相同的三个资产(同一份发布产物的副本)
- 如果
scan:guard失败,不要直接进入 release 流程
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

