Repository navigation
ci: fix dbt release detection in the release check - #346
Merged
Merged
Conversation
select_components.sh took the latest dbt-core version from the LATEST: line of `pip index versions`, an experimental command whose output no longer has that line. The version came out empty, counted as 0, and releases.json stayed at dbt 1.8.0 while PyPI has 1.12.6. The version now comes from PyPI's JSON API, and an empty result is reported as an error annotation instead of being silently ignored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: tnazarew <tomasz.nazarewicz@getindata.com>
tnazarew
marked this pull request as ready for review
October 21, 2026 21:29
tnazarew
force-pushed
the
ci/fix-dbt-release-check
branch
from
October 21, 2026 21:29
7ba24e8 to
c8fa07c
Compare
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.
The daily release check (
main_new_release.yml→scripts/select_components.sh) has never detected a dbt release after 1.8.0.generated-files/releases.jsonstill says 1.8.0, while PyPI has 1.12.6.Cause
The latest version was read from the
LATEST:line ofpip index versions dbt-core.pip indexis experimental, and its current output no longer has that line (it printsdbt-core (1.12.6)andAvailable versions: ...). So:latest_dbtcame out empty.version_sum ""evaluated to 0.There was no error anywhere, as the last run's log shows.
Fix
https://pypi.org/pypi/dbt-core/json,.info.version.::error::annotation and keeps the current version, instead of failing silently.Effect on the next daily run
releases.jsonis updated to 1.12.6, and 1.12.6 is added to the dbt matrix.csv_to_postgres, is limited to dbt1.8.0–1.8.0in itsconfig.json, so the dbt job finds no valid scenarios for 1.12.6. Testing newer dbt needs that limit raised, and possibly new expected events. That's a separate change.Testing
Ran
scripts/select_components.shlocally with a scratchGITHUB_OUTPUT. Output:ol_release=1.54.0,dbt_release=1.12.6,releases_updated=true, andupdated-releases.jsonhas dbt1.12.6.🤖 Generated with Claude Code