1. When Repeated Release Work Deserves a Shared Stream

    A worked release example shows how to separate shared build policy from product decisions, preserve immutable identity, and decide whether the added platform is worth owning.

  2. The Case for Publishing a Useful Package Early

    PyPI names are scarce, pending publishers do not reserve them, and active conflicts are hard to unwind. A small working release can be the responsible first public commitment.

  3. A Release Has Three Trust Decisions

    Version identity, permission to publish, and artifact integrity answer different questions. A release pipeline is trustworthy only when it connects all three.

← All writing