Skip to content

nextchanges: Prepare for upstream changes to tagging.py - #6029

Open
janniklasrose wants to merge 8 commits into
mainfrom
janniklasrose/nextchanges-prep-for-upstream-changes
Open

nextchanges: Prepare for upstream changes to tagging.py#6029
janniklasrose wants to merge 8 commits into
mainfrom
janniklasrose/nextchanges-prep-for-upstream-changes

Conversation

@janniklasrose

@janniklasrose janniklasrose commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Changes

Tagging logic currently in 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 🥞 : #6029 (this) > #6141 > #6036

Tests

Locally

@janniklasrose
janniklasrose marked this pull request as ready for review July 22, 2026 16:28
@janniklasrose
janniklasrose requested a review from pietern July 22, 2026 16:28
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: 899dce5

Run: 30809531056

Env 💚​RECOVERED 🙈​SKIP ✅​pass 🙈​skip Time
💚​ aws linux 4 4 309 1066 4:52
💚​ aws windows 4 4 311 1064 6:39
💚​ azure linux 4 4 308 1066 4:18
💚​ azure windows 4 4 310 1064 6:37
💚​ gcp linux 1 5 309 1066 5:12
💚​ gcp windows 1 5 311 1064 6:20
8 interesting tests: 4 RECOVERED, 4 SKIP
Test Name aws linux aws windows azure linux azure windows gcp linux gcp windows
💚​ TestAccept 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
🙈​ TestAccept/bundle/invariant/no_drift 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S
🙈​ TestAccept/bundle/resources/vector_search_endpoints/drift/recreated_same_name 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S
🙈​ TestAccept/bundle/resources/vector_search_indexes/recreate/embedding_dimension 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S
🙈​ TestAccept/ssh/connection 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S 🙈​S
💚​ TestFetchRepositoryInfoAPI_FromRepo 💚​R 💚​R 💚​R 💚​R 🙈​S 🙈​S
💚​ TestFetchRepositoryInfoAPI_FromRepo/root 💚​R 💚​R 💚​R 💚​R
💚​ TestFetchRepositoryInfoAPI_FromRepo/subdir 💚​R 💚​R 💚​R 💚​R
Top 3 slowest tests (at least 2 minutes):
duration env testname
5:19 azure windows TestAccept
5:18 aws windows TestAccept
5:17 gcp windows TestAccept

@pietern pietern left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is release_tagging.py still functional after tagging.py is updated?

@janniklasrose

janniklasrose commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

Is release_tagging.py still functional after tagging.py is updated?

Good question @pietern! TL;DR: identical behaviour, it's safe if we forget to cut over during the next genkit run.

Full explanation:

Once the upstream changes are merged, doing a generate without additional changes in CLI will continue to rewrite tagging.yml to run release_tagging.py.

our release_tagging.py monkey-patches the following methods to its own version:

  • get_next_tag_info
    • upstream changes will be ignored and release_tagging will function as it does now
  • clean_next_changelog
    • the upstream logic bypasses this method and runs a different one clean_nextchanges in the CLI repo
    • however, that upstream version will be identical to what we do currently

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 janniklasrose changed the title Prepare for upstream changes to tagging.py nextchanges: Prepare for upstream changes to tagging.py Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants