chore: release v3.5.3

[mise-en-dev]

📦️ Dependency Updates

• update jdx/pr-closer action to v1.1.0 by @renovate[bot] in #689

Summary by CodeRabbit

• Chores
  • Released version 3.5.3
  • Updated the jdx/pr-closer dependency to v1.1.0
  • Refreshed version and CLI documentation to reflect 3.5.3
  • Updated semver dependency and lockfile entries to the latest patch version

[coderabbitai]

📝 Walkthrough

Walkthrough

Version bumped from 3.5.2 to 3.5.3 across lib/Cargo.toml, cli/Cargo.toml, the root Cargo.toml workspace dependency, cli/usage.usage.kdl, docs/cli/reference/commands.json, docs/cli/reference/index.md, and CHANGELOG.md. Lockfile dependency for semver updated from 7.8.4 to 7.8.5 in aube-lock.yaml and package.json.

Changes

v3.5.3 Release Bump

Layer / File(s)	Summary
Version bump across Cargo manifests, CLI spec, docs, and CHANGELOG lib/Cargo.toml, cli/Cargo.toml, Cargo.toml, cli/usage.usage.kdl, docs/cli/reference/commands.json, docs/cli/reference/index.md, CHANGELOG.md	Package versions in all Rust manifests incremented to 3.5.3, workspace dependency for usage-lib updated to match, CLI spec and docs reference version fields updated, and a 3.5.3 CHANGELOG entry added with dependency update bullets.
Lockfile dependency updates for semver aube-lock.yaml, package.json	semver dependency bumped from 7.8.4 to 7.8.5 across root devDependencies, package resolution entries, snapshot references, and package.json.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• jdx/usage#688: Identical pattern of version bump across Cargo.toml, cli/Cargo.toml, lib/Cargo.toml, cli/usage.usage.kdl, and CLI docs for the preceding 3.5.1 → 3.5.2 release.
• jdx/usage#658: Earlier release-version bump updating the same manifest and spec version fields alongside lockfile maintenance.

Poem

🐇 Hippity hop, the version ticks up,
From .2 to .3, I filled up my cup!
The manifests match, the docs are aligned,
Dependencies bumped — neat, tidy, and signed.
Small patch, big joy — this bunny's content! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: release v3.5.3' accurately describes the pull request's primary purpose—releasing version 3.5.3 of the project.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}

[greptile-apps]

Greptile Summary

This is a routine release bump from v3.5.2 to v3.5.3, driven by a dependency update to jdx/pr-closer and a lockfile maintenance pass.

• Version strings updated consistently across all relevant files: Cargo.toml, cli/Cargo.toml, lib/Cargo.toml, Cargo.lock, cli/usage.usage.kdl, docs/cli/reference/commands.json, and docs/cli/reference/index.md.
• semver bumped from 7.8.4 → 7.8.5 in package.json and aube-lock.yaml, with integrity hashes updated accordingly.

Confidence Score: 5/5

Safe to merge — all changes are mechanical version bumps and lockfile updates with no logic modifications.

Every changed file is either a version string update, a generated artifact (CLI spec, reference docs), or a lock file reflecting the new versions. There are no code logic changes, no new dependencies beyond a patch-level semver bump, and all version references are consistent across the workspace.

No files require special attention.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds v3.5.3 release entry with dependency update notes
Cargo.toml	Bumps usage-lib version reference from 3.5.2 to 3.5.3
Cargo.lock	Lock file updated to reflect version bumps for usage-cli and usage-lib to 3.5.3
cli/Cargo.toml	Bumps usage-cli package version from 3.5.2 to 3.5.3
lib/Cargo.toml	Bumps usage-lib package version from 3.5.2 to 3.5.3
package.json	Updates semver dev dependency from ^7.8.4 to ^7.8.5
aube-lock.yaml	Lock file updated to reflect semver bump from 7.8.4 to 7.8.5
cli/usage.usage.kdl	Updates generated CLI spec version string to 3.5.3
docs/cli/reference/commands.json	Updates version field in generated CLI reference JSON to 3.5.3
docs/cli/reference/index.md	Updates version display in CLI reference docs to 3.5.3

_{Reviews (2): Last reviewed commit: "chore: release v3.5.3" | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Line 8: In the CHANGELOG.md file, line 8 contains duplicated wording where
"lock file maintenance lockfile maintenance" appears consecutively, which should
be simplified to just one instance of this phrase. Remove the redundant
repetition by keeping only a single occurrence of "lock file maintenance" (or
"lockfile maintenance" if that's the preferred format) in the bullet point
before the contributor attribution.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: e4d50ed0-ba77-4342-9f85-97d86764b67b

📥 Commits

Reviewing files that changed from the base of the PR and between 0250067 and 0028c19.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (9)

• CHANGELOG.md
• Cargo.toml
• aube-lock.yaml
• cli/Cargo.toml
• cli/usage.usage.kdl
• docs/cli/reference/commands.json
• docs/cli/reference/index.md
• lib/Cargo.toml
• package.json

✅ Files skipped from review due to trivial changes (7)

• Cargo.toml
• cli/Cargo.toml
• package.json
• cli/usage.usage.kdl
• docs/cli/reference/index.md
• docs/cli/reference/commands.json
• lib/Cargo.toml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix duplicated wording in lockfile maintenance bullet.

Line 8 repeats the same phrase (lock file maintenance lockfile maintenance), which reads as a typo in the release notes.

Suggested edit

-- lock file maintenance lockfile maintenance by [`@renovate`[bot]](https://github.com/renovate[bot]) in [`#691`](https://github.com/jdx/usage/pull/691)
+- lock file maintenance by [`@renovate`[bot]](https://github.com/renovate[bot]) in [`#691`](https://github.com/jdx/usage/pull/691)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- lock file maintenance lockfile maintenance by [@renovate[bot]](https://github.com/renovate[bot]) in [#691](https://github.com/jdx/usage/pull/691)
	- lock file maintenance by [`@renovate`[bot]](https://github.com/renovate[bot]) in [`#691`](https://github.com/jdx/usage/pull/691)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` at line 8, In the CHANGELOG.md file, line 8 contains duplicated
wording where "lock file maintenance lockfile maintenance" appears
consecutively, which should be simplified to just one instance of this phrase.
Remove the redundant repetition by keeping only a single occurrence of "lock
file maintenance" (or "lockfile maintenance" if that's the preferred format) in
the bullet point before the contributor attribution.