release-preflight

To validate a Python wheel before publishing, run pre-release validation that inspects wheel packaging, checks for leaked artifacts, and verifies core workflows run cleanly. This process confirms the build is safe, functional, and ready for publication.

Release preflight is a validation process for software projects that catches packaging mistakes, missing runtime files, and security gaps before a version goes public. You need it before merging a release PR or publishing to PyPI to confirm the build is safe.

You can check for API consistency and documentation drift by running consistency checks that compare the documented API against the actual package surface. This detects mismatches between the README and the installed package before publication.

Yes, you can test package installation behavior by installing the built package in a clean environment and exercising core workflows from a real user perspective. This user acceptance check confirms the runtime import validation and core workflow execution succeed.

You can scan your release build for security vulnerabilities by running a security and consistency review that scans for risky error handling and obvious dependency issues. This vulnerability scanning identifies security gaps before the version goes public.

The best way to prevent broken releases is to run full pre-release validation that confirms wheels and source distributions include the right files and exclude tests or leaked artifacts. This build verification ensures the release is ready for publication.