Merge pull request #172 from dwolfson/v6-prep

V6 prep - added data-engineer

Author: dwolfson

.github/workflows/release.yml

@@ -0,0 +1,51 @@
+name: Publish to PyPI and Release
+
+on:
+  push:
+    tags:
+      - 'v*' # Trigger on version tags like v1.0.0
+
+jobs:
+  test:
+    name: Run Tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+      - name: Set up Python
+        run: uv python install
+      - name: Install dependencies
+        run: uv sync --all-extras --dev
+      - name: Run unit tests
+        run: uv run pytest tests/ -m "not live_egeria"
+
+  build-n-publish:
+    name: Build and Publish to PyPI
+    needs: test
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      id-token: write # Required for OIDC trusted publishing
+      contents: write # Required to create GitHub Release
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v1
+        with:
+          files: dist/*
+          generate_release_notes: true
+          draft: false
+          prerelease: false

README.md

@@ -16,7 +16,7 @@ open source Egeria project can be found at [Egeria Project](https://egeria-proje
 
 This package is in active development. There is initial
 support for many of Egeria's services including configuration and operation.  This client depends on 
-This release supports Egeria 5.1 - although most of the functions may work on earlier versions of Egeria as well. 
+This release supports Egeria 6.0 - although most of the functions may work on earlier versions of Egeria as well. 
 
 The code is organized to mimic the existing Egeria Java Client structure.
 

RELEASING.md

@@ -0,0 +1,29 @@
+# Release Process for pyegeria
+
+We follow Semantic Versioning (SemVer). Releases are automated via GitHub Actions when a tag is pushed.
+
+## Steps to Release
+
+1.  **Update Version**: Update the version in `pyproject.toml`.
+    ```bash
+    # Example: bump to 1.1.0
+    sed -i 's/version = ".*"/version = "1.1.0"/' pyproject.toml
+    ```
+2.  **Commit and Push**:
+    ```bash
+    git add pyproject.toml
+    git commit -m "chore: release v1.1.0"
+    git push origin main
+    ```
+3.  **Create and Push Tag**:
+    ```bash
+    git tag v1.1.0
+    git push origin v1.1.0
+    ```
+4.  **Verify**:
+    *   Monitor the "Actions" tab in GitHub.
+    *   Once complete, the package will appear on [PyPI](https://pypi.org/project/pyegeria/) and a new Release will be visible on GitHub.
+
+## Best Practices
+- **PR Labels**: Use labels like `bug`, `enhancement`, and `documentation` on Pull Requests. The release notes generator uses these to categorize changes automatically.
+- **Trusted Publishing**: This repo uses OIDC. Ensure the GitHub environment `release` is configured in PyPI settings to allow publishing from this specific workflow.