Use hatch to build

.binder/environment.yml

@@ -1,6 +1,6 @@
 channels:
 - conda-forge
 dependencies:
+- hatchling =1.27.0
+- hatch-vcs =0.5.0
 - python >=3.11,<3.14
-- setuptools>=68
-- wheel

.ci_support/environment.yml

@@ -1,6 +1,6 @@
 channels:
 - conda-forge
 dependencies:
-- python >=3.11,<3.14
-- setuptools>=68
-- wheel
+- hatchling =1.27.0
+- hatch-vcs =0.5.0
+- python >=3.11,<3.14

.github/workflows/release-or-preview.yml

@@ -1,17 +1,17 @@
-# Dynamically updates the pyproject.toml for release to pypi
-# On PRs just lets you preview the new toml
-# On actual publication events, publishes to pypi
-name: Release (and/or preview)
+# This runs jobs which pyiron modules should run on release
+# This job runs on pull requests and does not actually publish anything to pypi
+# It is useful for debugging new build recipes
+# To actually release, change the `on` and `publish-to-pypi` fields
+name: Release
 
 on:
   pull_request:
   release:
     types: [ published ]
 
 jobs:
-  pyproject-flow:
-    uses: pyiron/actions/.github/workflows/pyproject-release.yml@actions-4.0.8
+  hatchling-release:
+    uses: pyiron/actions/.github/workflows/hatch-release.yml@actions-4.0.8
     secrets: inherit
     with:
-      semantic-upper-bound: 'minor'
       publish-to-pypi: ${{ github.event_name == 'release' && github.event.action == 'published' }}

docs/environment.yml

@@ -7,6 +7,6 @@ dependencies:
 - sphinx-gallery
 - sphinx-rtd-theme
 - versioneer
+- hatchling =1.27.0
+- hatch-vcs =0.5.0
 - python >=3.11,<3.14
-- setuptools>=68
-- wheel

pyiron_snippets/__init__.py

@@ -1,3 +1,8 @@
-from . import _version
+import importlib.metadata
 
-__version__ = _version.get_versions()["version"]
+try:
+    # Installed package will find its version
+    __version__ = importlib.metadata.version(__name__)
+except importlib.metadata.PackageNotFoundError:
+    # Repository clones will register an unknown version
+    __version__ = "0.0.0+unknown"