Update latest release in doc

lshaw8317 · lshaw8317 · commit 0ed6b02d2026 · 2026-03-03T11:39:17.000+01:00
diff --git a/RELEASING.rst b/RELEASING.rst
@@ -20,7 +20,7 @@ Preliminaries
         GIT_TAG b179abf1132dfa5a263b2ebceb6ef7a3c2890c64
     )
 
-  to point to the desired commit/tag in the c-blosc2 repo.
+  to point to the desired commit/tag in the c-blosc2 repo. Note that ``conda-forge`` only selects the latest release, so it may be necessary to do a formal release of ``c-blosc2`` to ensure that the package is correctly generated in ```conda-forge``.
 
 * Make sure that the current main branch is passing the tests in continuous integration.
 
diff --git a/doc/python-blosc2.rst b/doc/python-blosc2.rst
@@ -6,7 +6,7 @@
 
     <p style="text-align: center; color: black; background-color: rgba(230, 169, 9, 0.65);">
         <a href="https://github.com/Blosc/python-blosc2/blob/main/RELEASE_NOTES.md"
-           style="font-size: 1.5em;">Version 4.1.1 released on 2026-03-02!</a>
+           style="font-size: 1.5em;">Version 4.1.2 released on 2026-03-03!</a>
         <span style="display: inline-block; width: 20px;"></span>
         <span style="font-family: monospace;">pip install blosc2 -U</span>
     </p>

Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@ Preliminaries`
`20`	`20`	`GIT_TAG b179abf1132dfa5a263b2ebceb6ef7a3c2890c64`
`21`	`21`	`)`
`22`	`22`
`23`		`- to point to the desired commit/tag in the c-blosc2 repo.`
	`23`	+ to point to the desired commit/tag in the c-blosc2 repo. Note that ``conda-forge`` only selects the latest release, so it may be necessary to do a formal release of ``c-blosc2`` to ensure that the package is correctly generated in ```conda-forge``.
`24`	`24`
`25`	`25`	`* Make sure that the current main branch is passing the tests in continuous integration.`
`26`	`26`