Skip to content

ci(release): publish extras and compute-worker - #926

Merged
ParidelPooya merged 2 commits into
mainfrom
ci/publish-extras-compute-worker
Nov 10, 2026
Merged

ParidelPooya merged 2 commits into
mainfrom
ci/publish-extras-compute-worker

Conversation

@ParidelPooya

Copy link
Copy Markdown
Contributor

What

The release workflow now builds and publishes two more packages:

  • aws-durable-execution-sdk-python-extras
  • aws-durable-execution-sdk-python-compute-worker

RELEASING.md lists both, with their version files and the tag prefixes extras and compute-worker.

Why

  • Both names are on PyPI as prereleases: extras 0.1.0a0 and compute-worker 0.0.1a0. The upload claimed the names.
  • Each project has a trusted publisher for this repository, pypi-publish.yml, and the pypi environment.
  • So the workflow can publish later versions without a token.

Change

  • .github/workflows/pypi-publish.yml: both packages added to the release-build matrix (name and path) and to the pypi-publish matrix (name).
  • RELEASING.md:
    • Packages table: both packages, with tag prefixes extras and compute-worker.
    • Versioning: the path of each __about__.py.
    • Release Permissions and Protection: the patterns extras-v* and compute-worker-v*.
    • Tagging Convention and the checklist: examples for both prefixes.

Before the first release with these packages

  1. A repository admin adds extras-v* and compute-worker-v* to the pypi environment's deployment rules and to the protected tags ruleset. This PR documents the patterns. It cannot change those settings.
  2. The workflow publishes every package in the matrices on every release, whatever the tag prefix. So after this PR merges, the next release of any package also uploads extras 0.1.0 and compute-worker 0.0.1, the versions in their __about__.py files. Merge this PR when those two versions are ready to ship, or set their versions first.

Testing

  • Both matrices parse with yaml.safe_load, and each lists 6 packages in the same order.
  • Both packages build with hatch build, and check_dist_legal_files.py finds LICENSE and NOTICE in each distribution. The PyPI prereleases are those builds.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

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.
@ParidelPooya
ParidelPooya marked this pull request as ready for review November 10, 2026 20:35
@ParidelPooya
ParidelPooya merged commit e436a33 into main Nov 10, 2026
22 checks passed
@ParidelPooya
ParidelPooya deployed to ai-pr-review-runtime November 10, 2026 20:35 — with GitHub Actions Active
@ParidelPooya
ParidelPooya deleted the ci/publish-extras-compute-worker branch November 10, 2026 20:35

This branch was successfully deployed

1 active deployment
ai-pr-review-runtime — 6d739a0c Deployed Nov 10, 2026 by ParidelPooya via notify / Generate notification summary #407
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants