You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #1 ("Publish Silphe to PyPI as silphe") is still open, but silphe 0.1.0 has been live on PyPI since 2026-06-11, so the headline goal is met. It now sits alongside #62 (the 0.2.0 release) and it is not clear which one owns what.
Two of #1's own steps cannot be confirmed from outside the account:
Is a Trusted Publisher registered on the project?docs/0004-pypi-publish.md says to add one (owner martymcenroe, repo silphe, workflow release.yml, environment pypi) once the project exists. Whether that was ever done is unknown. It does not block the 0.2.0 upload, which is manual, but it is a prerequisite for the automated path in Land release.yml (OIDC release workflow) via classic-PAT — normal push blocked by PAT workflow scope #6 — and discovering it is missing at tag-push time is the worst moment to find out.
Was the post-publish verification ever run?Publish Silphe to PyPI as silphe #1 lists pip install silphe followed by silphe-play opening the green garden. No record that it happened.
Wanted
Check the PyPI project settings, then either resolve #1 as done or trim it down to whatever genuinely remains, so there is exactly one issue describing outstanding PyPI work.
Notes
Needs someone signed in to the PyPI account; not determinable from the repo.
Problem
Issue #1 ("Publish Silphe to PyPI as
silphe") is still open, butsilphe0.1.0 has been live on PyPI since 2026-06-11, so the headline goal is met. It now sits alongside #62 (the 0.2.0 release) and it is not clear which one owns what.Two of #1's own steps cannot be confirmed from outside the account:
docs/0004-pypi-publish.mdsays to add one (ownermartymcenroe, reposilphe, workflowrelease.yml, environmentpypi) once the project exists. Whether that was ever done is unknown. It does not block the 0.2.0 upload, which is manual, but it is a prerequisite for the automated path in Land release.yml (OIDC release workflow) via classic-PAT — normal push blocked by PAT workflow scope #6 — and discovering it is missing at tag-push time is the worst moment to find out.silphe#1 listspip install silphefollowed bysilphe-playopening the green garden. No record that it happened.Wanted
Check the PyPI project settings, then either resolve #1 as done or trim it down to whatever genuinely remains, so there is exactly one issue describing outstanding PyPI work.
Notes
Needs someone signed in to the PyPI account; not determinable from the repo.