Deploying to gh-pages from @ 020e167 🚀

Author: lucascolley

_sources/dev/releasing.md.txt

@@ -100,6 +100,11 @@
   docs update (the docs are published automatically from the sources on
   `main`).
 
+- [ ] **Bump the `__version__` attribute in `__init__.py`**
+
+  After an M.N.0 release, further development is towards version `M.(N+1).0`, thus the main branch's 
+  version is `M.(N+1).0.dev0`.
+
 - [ ] **Update conda-forge.**
 
   After the PyPI package is published, the conda-forge bot should update the

dev/releasing.html

@@ -319,6 +319,10 @@ <h1>Releasing<a class="headerlink" href="#releasing" title="Link to this heading
 docs update (the docs are published automatically from the sources on
 <code class="docutils literal notranslate"><span class="pre">main</span></code>).</p>
 </li>
+<li class="task-list-item enabled"><p><input class="task-list-item-checkbox"  type="checkbox"> <strong>Bump the <code class="docutils literal notranslate"><span class="pre">__version__</span></code> attribute in <code class="docutils literal notranslate"><span class="pre">__init__.py</span></code></strong></p>
+<p>After an M.N.0 release, further development is towards version <code class="docutils literal notranslate"><span class="pre">M.(N+1).0</span></code>, thus the main branch’s
+version is <code class="docutils literal notranslate"><span class="pre">M.(N+1).0.dev0</span></code>.</p>
+</li>
 <li class="task-list-item enabled"><p><input class="task-list-item-checkbox"  type="checkbox"> <strong>Update conda-forge.</strong></p>
 <p>After the PyPI package is published, the conda-forge bot should update the
 feedstock automatically after some time. The bot should automerge, so in