Strengthen release validation#34
Merged
eric-tramel merged 1 commit intoMay 7, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Strengthen
ddp check-release <plugin_name> <tag_version>so release validation now checks the plugin package metadata, release ref contract, checked-in schema v2 catalog entries for the releasing package, release-safe source metadata, docs URL metadata, and per-plugin CODEOWNERS release ownership.Why
A plugin release can currently pass with only version and basic PyPI metadata checks, leaving stale or incomplete
catalog/plugins.jsonentries, path-based catalog sources, mismatched git refs, or email-only CODEOWNERS to fail later or ship incorrect tap metadata. This makes release validation catch those problems before build and publish.Usage
For release-eligible CODEOWNERS, per-plugin
CODEOWNERSmay still include GitHub users, GitHub teams, or emails, but a releasable package must include at least one GitHub owner such as:Email-only ownership now fails
ddp check-releasewith a message that asks for a GitHub@useror@org/teamowner.How
ddp.catalogandddp.tap_confighelpers for PEP 440 versions, Python specifiers, directdata-designerdependency parsing, package paths, source object validation, docs slug generation, and release ref formatting.ddp.release_ownersmodule so publish CI authorization and local release validation use the same owner-token parsing path.Validation
make syncuv run pytest devtools/ddp/tests/test_validate_release.py -quv run pytest devtools/ddp/tests/test_codeowners.py -quv run pytest devtools/ddp/tests/ -quv run ruff check devtools/ddp/src/ddp/validate_release.py devtools/ddp/src/ddp/codeowners.py devtools/ddp/src/ddp/release_owners.py devtools/ddp/tests/test_validate_release.py devtools/ddp/tests/test_codeowners.pyuv run ruff format --check devtools/ddp/src/ddp/validate_release.py devtools/ddp/src/ddp/codeowners.py devtools/ddp/src/ddp/release_owners.py devtools/ddp/tests/test_validate_release.py devtools/ddp/tests/test_codeowners.pymake validate-release PLUGIN=data-designer-templatemake checkmake lintmake validate