Skip to content

fix(ci): pin pypi-publish to v1.14.3, drop finished setup todo - #12

Merged
sardi-dev merged 3 commits into
mainfrom
ci/pin-pypi-publish-v1.14.3
Oct 21, 2026
Merged

sardi-dev merged 3 commits into
mainfrom
ci/pin-pypi-publish-v1.14.3

Conversation

@sardi-dev

@sardi-dev sardi-dev commented Oct 21, 2026 •

Copy link
Copy Markdown
Owner

What and why

Three small follow-ups to #11, before the first PyPI release.

  • Pin the PyPI publish action to v1.14.3 (7245906, checked against the v1.14.3 tag in pypa/gh-action-pypi-publish). v1.14.2 bundles sigstore 4.5.0 and certifi 2025.8.3, which still trust the emSign root that was removed from CA bundles after the eMudhra incident. The publish job holds the PyPI token, so it should not run with a stale CA bundle.

  • Drop the "Repository setup" section from TODO.md. The GitHub settings (About, topics, social preview, Pages, Discussions, detection label, vulnerability reporting, ruleset for main, pypi environment) and the PyPI trusted publisher are in place, and CI runs now that the repository is public.

  • Make test_unclosed_orm_calls_parse_quickly independent of machine speed. It timed the parse against 5 seconds; the bounded parse takes 2 to 5 seconds depending on the machine, so it failed on a slow macOS runner (5.2 s) although the fix from fix(security): close the pre-publication audit findings #11 works. It now checks that every decorator call reads at most MAX_CALL_ARGS characters ahead. With that limit removed the test fails, as it should.

How I checked it

  • python -m pytest passes: 168 passed, 2 skipped (file symlinks cannot be made on this Windows machine)
  • For viewer changes: not applicable, no viewer change
  • Tried it on a real project: not applicable, workflow and docs only
  • CHANGELOG.md updated under Unreleased
  • gitleaks: no leaks in these commits

The workflow change is exercised by the first release tag (v0.3.1).

Ground rules

  • Nothing new is drawn or counted without a recorded connection or checked evidence
  • No secret values can reach archmap.json or the HTML
  • The page still loads nothing from the network

v1.14.2 bundles sigstore 4.5.0 and certifi 2025.8.3, which still trust
the emSign root that was removed after the eMudhra incident. The publish
job holds the PyPI token, so it should not run with a stale CA bundle.
@sardi-dev
sardi-dev merged commit 4e5a35d into main Oct 21, 2026
10 checks passed
@sardi-dev
sardi-dev deleted the ci/pin-pypi-publish-v1.14.3 branch October 21, 2026 14:34
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