Fix prepare-providers-documentation skill tag detection (dotted-id + sentinel/rc tags)#67921
Merged
potiuk merged 1 commit intoJun 2, 2026
Conversation
…otted-id tags, sentinel/rc exclusion)
jscheffl
approved these changes
Jun 2, 2026
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
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
prepare-providers-documentationagentic skill's Phase 2 / Incremental Phase 2 git query for the last release tag had two defects discovered during the 2026-06-02 release prep:providers-cncf-kubernetes/<ver>), but the skill built the tag pattern from the slash-converted folder path (providers-cncf/kubernetes/*) → matched no tags → empty commit lists for ~10 dotted providers.--sort=-v:refname | head -n1picks the99.98.0/99.99.0sentinel upper-bound tags and rc tags (git sorts1.2.0rc1after1.2.0) — e.g. yielding a bogus ~600-commit "amazon" range.Fixes both queries to derive the tag segment with
tr '.' '-', exclude99.9xsentinels andrcN, and adds a warning that breeze's Phase 1 discovery output is the authoritative commit set (the tag-based range can still diverge when a provider's latest final tag is not the last published release).Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines