From 629afa5146b13dbaec163325cf380155787b5c51 Mon Sep 17 00:00:00 2001
From: MotherSphere <mothersphere.colony@gmail.com>
Date: Tue, 27 Oct 2026 12:54:20 +0100
Subject: [PATCH] fix: bring Cargo.lock to 0.5.6 so locked builds work again

The 0.5.6 release pull request was merged nine seconds after it was
opened, before the release workflow had synced the lock onto it.
Cargo.toml says 0.5.6 while Cargo.lock still pinned both crates at
0.5.5, so every `--locked` build has failed since: CI's msrv job, the
release build of v0.5.6 and the PKGBUILD.
---
 Cargo.lock | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Cargo.lock b/Cargo.lock
index 5c5f115..b8745c1 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -2559,7 +2559,7 @@ checksum = "a611d15b50743feb4c76b7d03edcb0e64f399c26961e4efe6975bc398be6aa3d"
 
 [[package]]
 name = "raven"
-version = "0.5.5"
+version = "0.5.6"
 dependencies = [
  "anyhow",
  "clap",
@@ -2573,7 +2573,7 @@ dependencies = [
 
 [[package]]
 name = "raven-gui"
-version = "0.5.5"
+version = "0.5.6"
 dependencies = [
  "colony-ui",
  "iced",