From 12433e03443d36925a45421df9305ffb2c4194ab Mon Sep 17 00:00:00 2001
From: Patrick Collins <54278053+PatrickAlphaC@users.noreply.github.com>
Date: Sun, 17 Nov 2024 07:05:55 -0500
Subject: [PATCH] fix: docs for ignore-isolation (#157)

---
 docs/source/core_concepts/testing/staging_markers.rst | 6 ++++++
 uv.lock                                               | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/source/core_concepts/testing/staging_markers.rst b/docs/source/core_concepts/testing/staging_markers.rst
index f891701..2864a04 100644
--- a/docs/source/core_concepts/testing/staging_markers.rst
+++ b/docs/source/core_concepts/testing/staging_markers.rst
@@ -14,12 +14,17 @@ A lot of developers `should` run some sanity checks on a live network, for examp
 
 Maybe after you deploy your contracts, you want to run a quick test suite to make sure everything is ok, this is where "staging" tests come into play.
 
+.. note::
+
+    At this time, you also have to use ``@pytest.mark.ignore_isolation`` to work with titanoboa. 
+
 How to use staging markers
 ==========================
 
 .. code-block:: python
     
     @pytest.mark.staging 
+    @pytest.mark.ignore_isolation
     def test_staging_test(counter_contract):
         counter_contract.increment()
         assert counter_contract.number() == 2
@@ -70,6 +75,7 @@ To have a staging test also run on local and forked networks, you can do:
 .. code-block:: python
     
     @pytest.mark.staging
+    @pytest.mark.ignore_isolation
     @pytest.mark.local # See this!
     def test_staging_test(counter_contract):
         counter_contract.increment()
diff --git a/uv.lock b/uv.lock
index eb172af..f83ddc6 100644
--- a/uv.lock
+++ b/uv.lock
@@ -682,7 +682,7 @@ wheels = [
 
 [[package]]
 name = "moccasin"
-version = "0.3.4b2"
+version = "0.3.4b3"
 source = { editable = "." }
 dependencies = [
     { name = "pytest-cov" },