Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

The Day I Became the One Being pip Installed: My Pre-Release Checks Caught 3 Leaks

Описание и применение

Разработчик опубликовал CLI‑инструмент triage‑lens в PyPI, используя механические проверки, чтобы избежать утечек тестового кода, приватных репозиториев и некорректных ссылок. После публикации добавил проверки видимости версии и обновления README.

Задача

Ensuring that a Python package published to PyPI contains no unintended test code, private repo names, or broken links, and that post‑release artifacts are correctly reflected on PyPI.

Результат

All three pre‑release leaks were caught and fixed before publication, and post‑release checks prevented stale or missing releases from being exposed to users.

Рабочий процесс

  • 1. Configure GitHub Actions workflow for release
  • 2. Use Trusted Publishing (OIDC) for PyPI authentication
  • 3. Run mechanical pre‑release checks: exclude test files, verify no private repo name leaks, ensure README links are absolute
  • 4. Build distribution wheel and source archive
  • 5. Publish to PyPI
  • 6. Verify new version is visible to pip before running smoke test
  • 7. Update README on GitHub if needed and re‑publish if stale
  • 8. Monitor download counts and usage metrics

Доказательства

In this project, nothing goes out to a public repository without passing a mechanical check.

Источник

The packaging tool's default behavior had a path where the whole development test suite gets bundled along.

Источник

The name of my private development repository was about to appear in a published artifact.

Источник

The description shown on the PyPI page is baked into the artifact at the moment you publish.

Источник

  • Дата записи: 2026-09-05T18:15:02.694Z