Skip to content

Restore environment: pypi on the publish job - #12

Merged
mzargham merged 1 commit into
mainfrom
restore/publish-environment
Sep 19, 2026
Merged

mzargham merged 1 commit into
mainfrom
restore/publish-environment

Conversation

@mzargham

Copy link
Copy Markdown
Contributor

Restore environment: pypi on the publish job

v0.1.0 published successfully in March from BlockScience/knowledgecomplex with
environment: pypi. The May rebrand changed the repository claim GitHub sends,
while PyPI's trusted publisher still named the old owner, so publishing began
failing with invalid-publisher.

#11 read that as an environment problem and removed the environment. That
changed which claim was sent but not the one that was wrong, so the next attempt
failed identically, now reporting environment: MISSING.

The PyPI publisher is being repointed at DynamicalSystemsGroup/knowledgecomplex
with environment pypi — the configuration that worked before the rebrand, since
the owner was the only thing that ever changed. The pypi environment already
exists in this repository's settings, and keeping it keeps the gate: publishing
can be restricted to people who should release rather than being available to
anyone who can push a tag.

v0.1.0 published successfully in March from BlockScience/knowledgecomplex with
environment: pypi. The May rebrand changed the repository claim GitHub sends,
while PyPI's trusted publisher still named the old owner, so publishing began
failing with invalid-publisher.

#11 read that as an environment problem and removed the environment. That
changed which claim was sent but not the one that was wrong, so the next attempt
failed identically, now reporting environment: MISSING.

The PyPI publisher is being repointed at DynamicalSystemsGroup/knowledgecomplex
with environment pypi — the configuration that worked before the rebrand, since
the owner was the only thing that ever changed. The pypi environment already
exists in this repository's settings, and keeping it keeps the gate: publishing
can be restricted to people who should release rather than being available to
anyone who can push a tag.
@mzargham
mzargham merged commit 696b172 into main Sep 19, 2026
2 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.

1 participant