ci(release): publish audit_log, branding, keycloak to PyPI - #224
Closed
antosubash wants to merge 1 commit into
Closed
ci(release): publish audit_log, branding, keycloak to PyPI#224antosubash wants to merge 1 commit into
antosubash wants to merge 1 commit into
Conversation
These three module packages exist in the workspace and ship valid packaging metadata, but were never added to the `publish-pypi` matrix in release.yml — so every release since they were introduced skipped them and they're absent from PyPI (everything else is at v0.0.21). Add them to the matrix in alphabetical order within the module group. Verified locally: check_metadata passes and all three build to sdist+wheel with the force-included package.json present. First publish of a brand-new project name via Trusted Publishing requires a matching pending-publisher configured on pypi.org for each of simple_module_audit_log, simple_module_branding, simple_module_keycloak. Claude-Session: https://claude.ai/code/session_01Pf6ew7t9pHgR1fnZNew3Tc
Deploying simple-module-python with
|
| Latest commit: |
307eb9b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3f79e1f7.simple-module-python.pages.dev |
| Branch Preview URL: | https://worktree-publish-missing-pyp.simple-module-python.pages.dev |
Owner
Author
|
Splitting into three single-package PRs (one per package) as requested. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the three module packages that are present in the workspace but missing from the
publish-pypimatrix inrelease.yml, so they get published on the next release:simple_module_audit_logsimple_module_brandingsimple_module_keycloakWhy
Every other workspace package is on PyPI at v0.0.21. These three are not — the matrix was last touched when
simple_module_testwas added (#112), and audit_log (#185), keycloak (#184), and branding all landed afterward without being wired into the publish list. So each release silently skipped them.Verification (local, on this branch off origin/main)
scripts/check_metadata.py→ All package metadata OK.uv build --package <each>→ sdist + wheel built for all three.module.py,py.typed, and theforce-includedpackage.json.release.ymlparses as valid YAML; matrix now has 16 entries.simple_module_audit_log,simple_module_branding,simple_module_keycloakwith:antosubash, Repo:simple_module_pythonrelease.yml, Environment:pypireleaseworkflow (Actions → release → Run workflow). It bumps every package to the next version (0.0.22) and publishes the full matrix.fail-fast: falsemeans the existing packages still publish even if a new one's pending-publisher isn't set yet.https://claude.ai/code/session_01Pf6ew7t9pHgR1fnZNew3Tc