release: 0.17.0

[bompus]

Release prep for 0.17.0. No tag, GitHub release or npm publish in this pull request.

Version. 0.17.0, not 0.16.1. The two commits since v0.16.0 (1ff058b and db4216c) add one capability to a shipped script: check-open-work.mjs reports a new group and a new resolvedLater field in its --json output. That is a new feature, not a bug fix, and earlier minor releases (0.14.0, 0.15.0, 0.16.0) were cut for the same kind of change. It breaks nothing: the exit code and every existing group are unchanged.

What changes.

• CHANGELOG.md: ## Unreleased becomes ## 0.17.0 - 2026-10-17 with an empty ## Unreleased above it. The feature commit's entry and its fix (a commit made only of digits or letters) are one statement of final behavior, and it names the JSON field and the --repo condition for bare pull request numbers.
• package.json: 0.16.0 to 0.17.0.

Audits (release-batching.md).

• Accuracy audit: README, banners, overview image and its alt text, SECURITY.md and the docs. None of them names the open-work check, a version number or a count this release changes, and none of those files changed since the 0.16.0 audit (the diff since the tag touches the changelog, one skill's SKILL.md, its script and its test). No stale claim found.
• Changelog audit: every term in the new entry was checked against check-open-work.mjs: the group label, the resolvedLater field, the recheck: condition, the five token kinds, the 8-line cutoff, the "commit" or "sha" rule, the --repo rule, the plan-text-only run and the unchanged exit code.
• Not changed: rules/modifiers/plan-files.md tells the reader to check items the script lists as "possibly finished or due for a re-check". It stays accurate and does not name the new group; I left a shipped rule's text alone in a release-prep change.

Checks run locally, all exit 0. oxfmt@0.70.0 --check ., oxlint@1.85.0 . (one existing warning), node --test test/*.test.mjs (182 pass, 7 skipped), bun test test/ (558 tests, 0 fail), npm run check:package -- --bun (237 files), bun test skills/ (369 pass).

Landing follows the standing exception for review bots, plus the Greptile check read by hand; CI still has to be green.

---

Summary by cubic

Prepares the 0.17.0 release by bumping the version in package.json and updating CHANGELOG.md. The changelog entry consolidates the new resolvedLater group and the commit-matching fix into one statement of final behavior. No tag, GitHub release, or npm publish happens in this PR.

^{Written for commit 548a085. Summary will update on new commits.}

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 54aa9e3a-7a63-4f49-827c-e825580bce3f

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

[Low impact] This release-prep change appears safe to merge.

Summary

Prepares 0.17.0 without changing runtime code.

• The package and changelog now identify release 0.17.0.

No actionable issues found.

_{Reviews (1) · Last reviewed commit: "release: 0.17.0" · Reviewed by Greptile}