Skip to content

Release Python 1.0.0 (merge on 2026-09-15, once the repository is public) - #11

Merged
mwaisaida-13 merged 3 commits into
mainfrom
release/python-v1.0.0
Sep 16, 2026
Merged

mwaisaida-13 merged 3 commits into
mainfrom
release/python-v1.0.0

Conversation

@mwaisaida-13

@mwaisaida-13 mwaisaida-13 commented Sep 14, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Final PR before publishing developer-toolkit-elasticache 1.0.0 to PyPI, plus two repo-hygiene changes. Do not merge before the repository is public (planned 2026-09-15).

  • Remove the Private :: Do Not Upload classifier — the publish guard that makes python_dev.py verify fail and PyPI reject the upload.
  • Date the 1.0.0 changelog entry (2026-09-15; adjust if the release date moves).
  • CODEOWNERS: @aws/elasticache-devex owns the repository (validator: 0 errors). Enforcement needs "Require review from Code Owners" on branch protection — enabled separately.
  • .github/workflows/python.yml: top-level permissions: contents: read, matching node.yml / java.yml.

Merge conditions

  • Repository is public
  • pypi GitHub environment exists with required reviewers
  • PyPI pending trusted publisher registered (python-release.yml, environment pypi)

Verification

  • python scripts/python_dev.py ci — lint clean, 73 tests passed, wheel + sdist built, twine check --strict passed.
  • python scripts/python_dev.py verify python-v1.0.0 → Publishing version 1.0.0. (exit 0).
  • Python CI runs on this PR with the restricted token.

After merge

Create a GitHub Release tagged python-v1.0.0 targeting main. That triggers python-release.yml: matrix tests → verify → build → pypi environment approval → publish with attestations → smoke test.

@mwaisaida-13 mwaisaida-13 changed the title Prepare Python 1.0.0 release; add CODEOWNERS and CI token permissions Add CODEOWNERS and restrict the Python CI token to contents: read Sep 14, 2026
Removes the `Private :: Do Not Upload` classifier so PyPI accepts the
upload, and dates the 1.0.0 changelog entry. Merge only once the repository
is public; publishing is triggered by the python-v1.0.0 GitHub Release.
@mwaisaida-13 mwaisaida-13 changed the title Add CODEOWNERS and restrict the Python CI token to contents: read Release Python 1.0.0 (merge on 2026-09-15, once the repository is public) Sep 14, 2026
@mwaisaida-13
mwaisaida-13 marked this pull request as draft September 14, 2026 11:32
@mwaisaida-13
mwaisaida-13 marked this pull request as ready for review September 14, 2026 12:48
@mwaisaida-13
mwaisaida-13 merged commit 4b465f1 into main Sep 16, 2026
14 checks passed
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