nextchanges: Pull upstream tagging changes - #6141
Merged
Merged
Conversation
…ike in the upstream flow
Collaborator
Integration test reportCommit: d0f1f5c
11 interesting tests: 4 RECOVERED, 4 SKIP, 3 flaky
Top 3 slowest tests (at least 2 minutes):
|
…nges-prep-for-upstream-changes
The wrapper is removed later in this stack, so naming the file here goes stale; the behavior it describes is what matters. Co-authored-by: Isaac
janniklasrose
force-pushed
the
janniklasrose/regenerate-tagging
branch
from
August 3, 2026 11:26
876195b to
d0f1f5c
Compare
janniklasrose
changed the base branch from
main
to
janniklasrose/nextchanges-prep-for-upstream-changes
August 3, 2026 11:26
This was referenced Aug 3, 2026
janniklasrose
changed the title
denik
approved these changes
Aug 5, 2026
Base automatically changed from
janniklasrose/nextchanges-prep-for-upstream-changes
to
main
August 5, 2026 11:24
janniklasrose
added a commit
that referenced
this pull request
Aug 5, 2026
> [!CAUTION] > Do not merge until upstream changes to tagging.yml and tagging.py are landed and consumed Remove release_tagging.py wrapper and cut over to tagging.py for .nextchanges/ handling CI on Changelog Preview will continue to fail until the cutover because the current tagging.py doesn't support/respect `--preview`. Stack 🥞 : #6029 > #6141 > #6036 (this)
janniklasrose
added a commit
to GrantIsEaton/cli
that referenced
this pull request
Aug 5, 2026
) ## Changes Tagging logic currently in [release_tagging.py](https://github.com/databricks/cli/blob/main/internal/genkit/release_tagging.py) is being upstreamed. This includes README.md inside a fragment being treated as a normal fragment and reading the sections from .codegen.json. Once upstream changes land, they will make their way into CLI via the next run of genkit. We will then be able to drop release_tagging.py and change tagging.yml rewrite to point back at tagging.py. ## Why Align with upcoming upstream changes. Stack 🥞 : databricks#6029 (this) > databricks#6141 > databricks#6036 ## Tests Locally
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
3 participants
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.
Changes
task generate-clijsonWhy
We upstreamed our release tagging logic.
Stack 🥞 : #6029 > #6141 (this) > #6036