From 4911b0641b2c12580f97c22362cc0683dfd9f8a0 Mon Sep 17 00:00:00 2001
From: Dima Tisnek <dima.tisnek@canonical.com>
Date: Fri, 31 Jan 2025 06:54:22 +0900
Subject: [PATCH] fix: require today's ops for today's ops-scenario (#1551)

and prep for release

the idea is that we'd:
- release this as `ops-scenario=7.1.1`
- yank `ops-scenario=7.1.0`

the users can then either stay on old ops and old ops-scenario, or
upgrade both
the automatic version resolution should work, I think :)
---
 testing/CHANGES.md     | 6 ++++++
 testing/pyproject.toml | 4 ++--
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/testing/CHANGES.md b/testing/CHANGES.md
index f14e586be..bce19b7f4 100644
--- a/testing/CHANGES.md
+++ b/testing/CHANGES.md
@@ -1,3 +1,9 @@
+# 7.1.1 - 30 Jan 2025
+
+## Fixes
+
+* require ops 2.18.0 or better as a hot-fix against accidentally introduced incompatibility (#1551)
+
 # 7.1.0 - 30 Jan 2025
 
 ## Features
diff --git a/testing/pyproject.toml b/testing/pyproject.toml
index 369c52c74..4ffe949a1 100644
--- a/testing/pyproject.toml
+++ b/testing/pyproject.toml
@@ -8,7 +8,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "ops-scenario"
 
-version = "7.2.0.dev0"
+version = "7.1.1"
 
 authors = [
     { name = "Pietro Pasotti", email = "pietro.pasotti@canonical.com" }
@@ -21,7 +21,7 @@ license.text = "Apache-2.0"
 keywords = ["juju", "test"]
 
 dependencies = [
-    "ops~=2.17",
+    "ops~=2.18",
     "PyYAML>=6.0.1",
 ]
 readme = "README.md"