[github-actions]

Prepare v0.6.0.

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 0.6.0 with expanded display control and improved DRM and Wayland reliability.

New Features:

• Add the v0.6.0 release with display-binding and IPC support.

Bug Fixes:

• Improve DRM and Wayland display handling, including hotplug recovery, rendering synchronization, cursor support, layer stacking, focus, and fullscreen transitions.

Enhancements:

• Clarify lid behavior and separate requested output state from lid suppression.
• Refine DRM output management and modularize runtime responsibilities.

Build:

• Update the project and Arch package versions to 0.6.0.

Documentation:

• Document the v0.6.0 changes in the changelog.

[sourcery-ai]

Reviewer's Guide

This release-preparation PR updates all project and Arch packaging version metadata from 0.5.2 to 0.6.0, refreshes the lockfile, and adds a categorized CHANGELOG entry covering the release’s display, lid-policy, DRM, Wayland, and rendering changes.

File-Level Changes

Change	Details	Files
Bump the project and package metadata to the v0.6.0 release.	Update the Cargo package version and lockfile metadata. Update both Arch package recipes to use the new version.	Cargo.toml Cargo.lock packaging/arch/PKGBUILD packaging/arch-bin/PKGBUILD
Publish the v0.6.0 changelog with categorized release notes and comparison metadata.	Add the release date and v0.5.2 comparison link. Document new display/IPC functionality, lid/output-state changes, DRM and Wayland fixes, and other release work.	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

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: bc0348f3-4f8c-475e-9bff-15af8ba3e80e

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.5.2"
+version = "0.6.0"
 dependencies = [
  "anyhow",
</code_context>
<issue_to_address>
**Release publication runs twice**

When the prepared release commit is merged into `main` and the branch-triggered and tag-triggered runs overlap, `determine-release.sh` creates and pushes the `v0.6.0` tag while the branch-triggered release workflow continues; the tag push starts a second workflow, and both runs publish the same release assets, causing the concurrent uploads to collide and a release run to fail or leave incomplete artifacts.

Avoid triggering a second publishing run for tags created by the branch workflow, or serialize and deduplicate publication for each version.
</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]

🟡 Medium · Release publication runs twice

When the prepared release commit is merged into main and the branch-triggered and tag-triggered runs overlap, determine-release.sh creates and pushes the v0.6.0 tag while the branch-triggered release workflow continues; the tag push starts a second workflow, and both runs publish the same release assets, causing the concurrent uploads to collide and a release run to fail or leave incomplete artifacts.

Avoid triggering a second publishing run for tags created by the branch workflow, or serialize and deduplicate publication for each version.

Prompt for AI agents

In `Cargo.toml` at line 3:

**Release publication runs twice**

When the prepared release commit is merged into `main` and the branch-triggered and tag-triggered runs overlap, `determine-release.sh` creates and pushes the `v0.6.0` tag while the branch-triggered release workflow continues; the tag push starts a second workflow, and both runs publish the same release assets, causing the concurrent uploads to collide and a release run to fail or leave incomplete artifacts.

Avoid triggering a second publishing run for tags created by the branch workflow, or serialize and deduplicate publication for each version.