From d2d699d87d731aabd8396d1426a0f60cee97721f Mon Sep 17 00:00:00 2001 From: Pooya Paridel Date: Tue, 10 Nov 2026 18:44:35 +0000 Subject: [PATCH] ci(release): publish extras and compute-worker The extras and compute-worker packages are now on PyPI as prereleases, with a trusted publisher for pypi-publish.yml. The workflow now builds and publishes both packages. RELEASING.md lists them, with the tag prefixes extras and compute-worker. --- .github/workflows/pypi-publish.yml | 6 ++++++ RELEASING.md | 13 ++++++++++++- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/.github/workflows/pypi-publish.yml b/.github/workflows/pypi-publish.yml index ea2ef48b4..921d872b4 100644 --- a/.github/workflows/pypi-publish.yml +++ b/.github/workflows/pypi-publish.yml @@ -30,6 +30,10 @@ jobs: path: packages/aws-durable-execution-sdk-python-testing - name: aws-durable-execution-sdk-python-telemetry-exporter path: packages/aws-durable-execution-sdk-python-telemetry-exporter + - name: aws-durable-execution-sdk-python-extras + path: packages/aws-durable-execution-sdk-python-extras + - name: aws-durable-execution-sdk-python-compute-worker + path: packages/aws-durable-execution-sdk-python-compute-worker steps: - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 @@ -67,6 +71,8 @@ jobs: - name: aws-durable-execution-sdk-python-otel - name: aws-durable-execution-sdk-python-testing - name: aws-durable-execution-sdk-python-telemetry-exporter + - name: aws-durable-execution-sdk-python-extras + - name: aws-durable-execution-sdk-python-compute-worker permissions: id-token: write diff --git a/RELEASING.md b/RELEASING.md index 3a54f80bd..23daa6087 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -12,6 +12,8 @@ This monorepo contains the following packages: | `aws-durable-execution-sdk-python-otel` | `packages/aws-durable-execution-sdk-python-otel` | `otel` | | `aws-durable-execution-sdk-python-testing` | `packages/aws-durable-execution-sdk-python-testing` | `testing` | | `aws-durable-execution-sdk-python-telemetry-exporter` | `packages/aws-durable-execution-sdk-python-telemetry-exporter` | `telemetry-exporter` | +| `aws-durable-execution-sdk-python-extras` | `packages/aws-durable-execution-sdk-python-extras` | `extras` | +| `aws-durable-execution-sdk-python-compute-worker` | `packages/aws-durable-execution-sdk-python-compute-worker` | `compute-worker` | ## Versioning @@ -21,6 +23,8 @@ Each package maintains its own version in its respective `__about__.py` file: - OTel: `packages/aws-durable-execution-sdk-python-otel/src/aws_durable_execution_sdk_python_otel/__about__.py` - Testing: `packages/aws-durable-execution-sdk-python-testing/src/aws_durable_execution_sdk_python_testing/__about__.py` - Telemetry Exporter: `packages/aws-durable-execution-sdk-python-telemetry-exporter/src/aws_durable_execution_sdk_python_telemetry_exporter/__about__.py` +- Extras: `packages/aws-durable-execution-sdk-python-extras/src/aws_durable_execution_sdk_python_extras/__about__.py` +- Compute Worker: `packages/aws-durable-execution-sdk-python-compute-worker/src/aws_durable_execution_sdk_python_compute_worker/__about__.py` Set the release version in the appropriate `__about__.py` file(s) and merge to `main` before creating a release. Use a new version for an existing distribution, @@ -34,6 +38,8 @@ The GitHub `pypi` environment permits deployments only from **tags** matching: - `otel-v*` - `testing-v*` - `telemetry-exporter-v*` +- `extras-v*` +- `compute-worker-v*` Branches, including `main` and temporary publishing branches, are not allowed. GitHub checks the workflow run's ref; checking out an allowed tag or a merged @@ -184,6 +190,8 @@ The tag should be the version of the package being bumped, prepended with a desc - **OTel only:** `otel-v` (e.g., `otel-v0.3.0`) - **Testing only:** `testing-v` (e.g., `testing-v1.2.1`) - **Telemetry Exporter only:** `telemetry-exporter-v` (e.g., `telemetry-exporter-v1.0.0`) +- **Extras only:** `extras-v` (e.g., `extras-v0.1.0`) +- **Compute Worker only:** `compute-worker-v` (e.g., `compute-worker-v0.0.1`) - **Multiple packages in a single release:** comma-separate the sub-tags (e.g., `sdk-v1.6.0,otel-v0.3.0`) Examples: @@ -193,6 +201,8 @@ sdk-v1.6.0 otel-v0.3.0 testing-v1.2.1 telemetry-exporter-v1.0.0 +extras-v0.1.0 +compute-worker-v0.0.1 sdk-v1.6.0,otel-v0.3.0 ``` @@ -360,7 +370,8 @@ Before publishing a release: ruleset - [ ] Release notes written with separate sections per package - [ ] Tag follows the naming convention (`sdk-vX.Y.Z`, `otel-vX.Y.Z`, `testing-vX.Y.Z`, - `telemetry-exporter-vX.Y.Z`, or comma-separated) + `telemetry-exporter-vX.Y.Z`, `extras-vX.Y.Z`, `compute-worker-vX.Y.Z`, + or comma-separated) After publishing a release: