You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
release: CHANGELOG stops at 1.5.0, changesets are unconsumed, and 1.9.8 has no tag or release #70
package.json and npm are at 1.9.8. CHANGELOG.md has an Unreleased block followed directly by 1.5.0; there are no entries for 1.6.0 through 1.9.8.
.changeset/ holds four pending changesets (agent-reliability-and-batch-render, converter-sandbox-runtime, native-office-review, safe-office-data-and-review), so releases are being cut without changeset version consuming them.
Git tags run through v1.9.7; there is no v1.9.8 tag.
GitHub Releases exist for 1.9.1, 1.9.2, 1.9.4, 1.9.6 and 1.9.7. 1.9.3, 1.9.5 and 1.9.8 have none.
skills/deckuse/SKILL.md frontmatter still has metadata.version: '1.5.0'.
The repository description is "A local-first structural editing engine for PPTX files." and the topics are agent, deck, office, pptx. DOCX support and the coding-agent focus are not reflected.
Impact
Users and agents cannot tell what changed between the version they have and the latest one. The README tells agents to install a skill "from the release tag matching the npm package version", which is not possible for 1.9.8.
Acceptance
scripts/release.sh consumes changesets (or the changeset flow is dropped and the CHANGELOG is written another way) so every published version has an entry.
CHANGELOG is backfilled for 1.6.0–1.9.8, at least at one line per release.
Every published npm version has a matching git tag and GitHub Release; the release script fails if the tag is missing.
The skill metadata version is generated from package.json or removed.
Repository description and topics mention DOCX and agent use.
Activity
zhaoxiongfei commentedon Nov 13, 2026
已补齐 1.6.0–1.9.8 CHANGELOG,处理已覆盖的 changeset,删除过期的 Skill 版本字段,更新仓库简介和主题。发布脚本要求 CHANGELOG 对应版本和指向 HEAD 的标签。实测缺标签时拒绝发布。当前仓库的 Releases API 返回空列表,npm 1.9.8 也没有 gitHead,发布时间早于候选发布提交的提交时间。该候选的 README、Skill 和依赖信息与 npm 包相符,完整源码对应关系尚待确认。请保留此 issue 以核对历史标签和补发 GitHub Releases。
已随 PR #74 合并到 main(46ff80d)。GitHub 两组 CI、本地 470 项测试和 npm 安装包检查通过。
#74
zhaoxiongfei commentedon Nov 14, 2026
已核对远端 v1.9.8 指向 faf1d88,v1.9.9 指向 476d91e,标签内的 package.json 版本与标签一致。1.9.9 的 CHANGELOG 已包含本次发布条目,已发布的 changeset 已清理。
本轮补建并核验了 19 个 GitHub Release,包括 1.6.0 至 1.9.9 的全部 13 个版本。1.9.9 为最新 Release。历史数据使用现有标签,其中 v1.4.1 的标签依据 npm 的 gitHead 和对应源码版本补建。
#70 仍保持开放。早期 npm 版本还有 9 个缺少可核验的匹配标签或 Release。以 1.3.1 为例,npm 的 gitHead 所指源码 manifest 仍写 1.3.0,需要额外的发布记录来确认源码对应关系。
GitHub Releases