docs: add release process documentation (#90)

* Initial plan

* docs: add Deploying New Releases section to development documentation

Co-authored-by: kjy5 <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: kjy5 <[email protected]>

Author: Copilot

docs/home/development.md

@@ -26,3 +26,25 @@ hatch run check
 ```
 
 to run pyright type checking.
+
+## Deploying New Releases
+
+Deploying a new release is done automatically via GitHub Actions. To deploy a new release:
+
+1. Update the version number in `src/vbl_aquarium/__about__.py`
+2. Commit and push the version change to the `main` branch
+3. Create and push a tag with the version number:
+
+```bash
+git tag v<version>
+git push origin v<version>
+```
+
+The [release workflow](https://github.com/VirtualBrainLab/vbl-aquarium/blob/main/.github/workflows/release.yml) will automatically:
+
+- Build the package using Hatch
+- Publish the package to [PyPI](https://pypi.org/project/vbl-aquarium/)
+- Create a GitHub release with auto-generated release notes
+
+!!! note
+    Pre-release versions (containing `a`, `b`, `c`, or `d` in the version string) will be marked as pre-releases on GitHub.