[github-actions]

Prepare v0.7.1.

This PR is generated by .github/scripts/prepare-release.py and updates:

• Cargo.toml
• Cargo.lock
• CHANGELOG.md
• packaging/arch/PKGBUILD
• packaging/arch-bin/PKGBUILD

Summary by Sourcery

Release instantWM version 0.7.1 with platform, input, display, and game-switching fixes.

Bug Fixes:

• Document fixes for postmarketOS builds, hybrid multi-GPU tablet startup, game switching, pointer constraints, monitor rotation, and touchscreen behavior.

Enhancements:

• Document removal of redundant input and rendering work and other usability fixes, including stacked-monitor bar visibility and shared terminal launching.

Build:

• Bump the project and Arch package versions to 0.7.1.

Documentation:

• Add the v0.7.1 changelog entry.

Chores:

• Update the locked dependency metadata for the 0.7.1 release.

[sourcery-ai]

Reviewer's Guide

This release-preparation PR updates all tracked package and packaging metadata from 0.7.0 to 0.7.1 and adds the 0.7.1 changelog entry with the release date, improvements, fixes, and other included changes.

File-Level Changes

Change	Details	Files
Bump the project release version to 0.7.1 across Rust metadata, lockfile, and Arch packaging.	Update the package version in Cargo metadata and regenerate the corresponding lockfile entry. Update package versions for source and prebuilt Arch packages.	Cargo.toml Cargo.lock packaging/arch/PKGBUILD packaging/arch-bin/PKGBUILD
Document the 0.7.1 release and its included fixes and improvements.	Add the dated 0.7.1 comparison link and categorize changes under Changed, Fixed, and Other.	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: f6fcf039-b765-4cd3-b29d-752314c377ac

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

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

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="Cargo.toml" line_range="3" />
<code_context>
 [[package]]
 name = "instantwm"
-version = "0.7.0"
+version = "0.7.1"
 dependencies = [
  "anyhow",
</code_context>
<issue_to_address>
**Release runs publish twice**

When the merged release commit triggers the main-branch workflow, `determine-release.sh` pushes `v0.7.1`, starting a tag-triggered workflow while the branch-triggered workflow also sets `should_release=true`; both run `softprops/action-gh-release` for the same tag, so they race to create the release and upload identical assets, causing one release job to fail or overwrite assets.

Ensure only one of the branch-triggered or tag-triggered workflows publishes a given release.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: Cargo.toml:3

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

🟠 High · Release runs publish twice

When the merged release commit triggers the main-branch workflow, determine-release.sh pushes v0.7.1, starting a tag-triggered workflow while the branch-triggered workflow also sets should_release=true; both run softprops/action-gh-release for the same tag, so they race to create the release and upload identical assets, causing one release job to fail or overwrite assets.

Ensure only one of the branch-triggered or tag-triggered workflows publishes a given release.

Prompt for AI agents

In `Cargo.toml` at line 3:

**Release runs publish twice**

When the merged release commit triggers the main-branch workflow, `determine-release.sh` pushes `v0.7.1`, starting a tag-triggered workflow while the branch-triggered workflow also sets `should_release=true`; both run `softprops/action-gh-release` for the same tag, so they race to create the release and upload identical assets, causing one release job to fail or overwrite assets.

Ensure only one of the branch-triggered or tag-triggered workflows publishes a given release.