chore(main): release 0.10.1

[kerryhatcher]

Release the AppImage packaging fix as v0.10.1. This manual release PR is necessary because the current Release Please manifest only tracks app/, while the zsync correction was in packaging/.\n\nValidated with the required just run smoke launch.

[coderabbitai]

Warning

Review limit reached

@kerryhatcher, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 60e14a7c-7a47-45b8-a452-aa9639980e18

📥 Commits

Reviewing files that changed from the base of the PR and between 3254938 and 1b455fb.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• .release-please-manifest.json
• app/CHANGELOG.md
• app/Cargo.toml

---

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.}

[Copilot]

🟢 Approval recommended

The changes are limited to consistent version/changelog/manifest updates with no functional code modifications detected.

Pull request overview

This PR performs the manual version bump and release metadata updates needed to ship v0.10.1, ensuring Release Please’s app/-tracked manifest and the crate version/changelog are consistent after a packaging-only fix.

Changes:

• Bump rustywx version from 0.10.0 to 0.10.1 in the crate and lockfile.
• Add the 0.10.1 changelog entry referencing the AppImage zsync metadata fix.
• Update .release-please-manifest.json to track the new app version.

File summaries

File	Description
Cargo.lock	Updates the locked package version for rustywx to 0.10.1.
app/CHANGELOG.md	Adds the v0.10.1 release notes entry and compare/commit links.
app/Cargo.toml	Bumps the crate version to 0.10.1.
.release-please-manifest.json	Updates Release Please manifest to app: 0.10.1.

Review details

• Files reviewed: 3/4 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1b455fb567

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Route the manual bump through a release-producing path

When this hand-authored release commit lands on main, Release Please will not treat it as the managed pending release PR whose merge creates a tag; nevertheless, this line records 0.10.1 as already released. In the inspected .github/workflows/release-please.yml, both artifact builds and crate publishing require the action's releases_created output, while the recovery path requires an existing tag, so neither path runs: v0.10.1, the fixed AppImages/zsync files, and the crate are never published, and subsequent automation starts from an incorrect baseline. Generate and merge a Release Please release PR, or explicitly create the tag and invoke the recovery workflow, rather than advancing the manifest alone.

Useful? React with 👍 / 👎.