fix: validate PyPI availability against dbt-core, not dbt - #16324
Open
ash2shukla wants to merge 1 commit into
Open
ash2shukla wants to merge 1 commit into
ash2shukla wants to merge 1 commit into
Conversation
Run 34997786343 failed validate-package-available-pypi for a 1.12.5 release with "The info about dbt v1.12.5 version is not available in PyPI", even though dbt-core==1.12.5 was live on PyPI. This repo was renamed from dbt-core to dbt, but it still builds and publishes the dbt-core package (core/pyproject.toml: name = "dbt-core"). The shared pypi-release.yml workflow derives the PyPI package name from the repo name by default, which is now wrong for this repo. Requires dbt-labs/dbt-release#173 (adds the package_name input) to be merged first. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
1.12.5, target branch1.latest) failed atPyPI Release / validate-package-available-pypi:dbt-coretodbt(GitHub transparently redirects the old repo name/URLs, but it's the same repo — same repo ID). It still builds and publishes thedbt-corePyPI package (core/pyproject.toml:name = "dbt-core"), not a package literally nameddbt. The sharedpypi-release.ymlreusable workflow (indbt-labs/dbt-release) derives the PyPI package name to validate fromgithub.event.repository.name, which is nowdbtfor this repo — so it was checking PyPI for the wrong package name entirely (a legacy, unrelateddbtpackage that stopped tracking dbt-core's 1.x versioning long ago).dbt-corepackage itself published fine. But it will keep failing every release triggered from this repo until fixed, always requiring manual intervention.package_name: "dbt-core"to thepypi-releasejob in.github/workflows/release.yml, using the new override input added in dbt-labs/dbt-release#173.Dependency
This PR requires dbt-labs/dbt-release#173 to be merged first (adds the
package_nameinput topypi-release.yml). Until that merges,@mainwon't recognize this input and the release workflow will fail with an unrecognized-input error.Test plan
validate-package-available-pypichecks PyPI fordbt-core, notdbt🤖 Generated with Claude Code