add: workflow for dev release

Author: LennartPurucker

.github/workflows/dev-release.yaml

@@ -0,0 +1,60 @@
+name: Dev Release
+
+# AutoGluon-style: publish a `.devN` build to PyPI for every successful push
+# to `main`. No git tag, no commit, no GitHub Release — the version is
+# computed on the runner and exists only on PyPI.
+#
+# Gated on the Tests workflow succeeding for that commit, so a broken main
+# does not get published.
+
+on:
+  workflow_run:
+    workflows: ["Tests"]
+    types: [completed]
+    branches: [main]
+
+jobs:
+  publish-dev:
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write   # (future) PyPI trusted publishing via OIDC
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.workflow_run.head_sha }}
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Set up Python
+        run: uv python install 3.11
+
+      - name: Compute .dev version
+        id: ver
+        run: |
+          base="$(uv version --short)"
+          if [[ ! "$base" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+            echo "::error::pyproject version '$base' is not a plain X.Y.Z; refusing to derive a dev version"
+            exit 1
+          fi
+          IFS=. read -r major minor patch <<<"$base"
+          next="${major}.${minor}.$((patch + 1))"
+          # PEP 440: <next-release>.dev<UTC timestamp>. Sorts before <next-release>
+          # and after any prior release. Strictly monotonic across commits.
+          ts="$(date -u +%Y%m%d%H%M%S)"
+          version="${next}.dev${ts}"
+          echo "version=$version" >> "$GITHUB_OUTPUT"
+          echo "Publishing dev version: $version (base $base, commit ${{ github.event.workflow_run.head_sha }})"
+
+      - name: Set version (ephemeral, not committed)
+        run: uv version "${{ steps.ver.outputs.version }}"
+
+      - name: Build sdist + wheel
+        run: uv build
+
+      - name: Publish to PyPI
+        env:
+          UV_PUBLISH_TOKEN: ${{ secrets.PYPI_TOKEN }}
+        run: uv publish

.github/workflows/prerelease.yaml

@@ -0,0 +1,50 @@
+name: Prerelease
+
+# Publish a PEP 440 prerelease (alpha/beta/rc/dev) to PyPI WITHOUT creating a
+# git tag, commit, or GitHub Release. The version is set on the runner only;
+# nothing is pushed back to the repo.
+#
+# Trigger from the Actions UI:
+#   Actions -> Prerelease -> Run workflow -> enter version (e.g. 0.0.4a1)
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Prerelease version (e.g. 0.0.4a1, 0.0.4b2, 0.0.4rc1, 0.0.4.dev3)"
+        required: true
+        type: string
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write   # (future) PyPI trusted publishing via OIDC
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Set up Python
+        run: uv python install 3.11
+
+      - name: Reject stable versions
+        run: |
+          v="${{ inputs.version }}"
+          if [[ ! "$v" =~ [a-z] ]]; then
+            echo "::error::'$v' has no prerelease segment. Use the Release workflow (push a v$v tag) for stable releases."
+            exit 1
+          fi
+
+      - name: Set version (ephemeral, not committed)
+        run: uv version "${{ inputs.version }}"
+
+      - name: Build sdist + wheel
+        run: uv build
+
+      - name: Publish to PyPI
+        env:
+          UV_PUBLISH_TOKEN: ${{ secrets.PYPI_TOKEN }}
+        run: uv publish

DEVELOPMENT.md

@@ -49,6 +49,30 @@ in two situations:
   match the version in `pyproject.toml`, so the bump and the tag must
   agree.
 
+### Prereleases (no git tag)
+
+Two flavors, both publish to PyPI without creating a git tag, commit, or
+GitHub Release. The version is set only on the CI runner.
+
+**Automatic `.dev` builds on every push to `main`** —
+[`.github/workflows/dev-release.yaml`](.github/workflows/dev-release.yaml).
+Triggered via `workflow_run` after the `Tests` workflow succeeds. The
+version is computed as `<next-patch>.dev<UTC-timestamp>` (e.g.
+`0.0.4.dev20260528170102` when `pyproject.toml` is at `0.0.3`). This is
+the AutoGluon-style "every commit is on PyPI" pattern — install with:
+
+```bash
+pip install --pre data-foundry        # any prerelease
+pip install data-foundry==0.0.4.dev*  # a specific dev cycle
+```
+
+**Manual `alpha`/`beta`/`rc` from the Actions UI** —
+[`.github/workflows/prerelease.yaml`](.github/workflows/prerelease.yaml).
+Go to `Actions → Prerelease → Run workflow`, enter a PEP 440 prerelease
+version (e.g. `0.0.4a1`, `0.0.4b2`, `0.0.4rc1`), and it publishes that
+exact version. Stable `X.Y.Z` inputs are rejected — use the tag-push
+release flow for those.
+
 ### One-time setup
 
 * Add a `PYPI_TOKEN` secret in the GitHub `pypi` environment