Uh oh!
There was an error while loading. Please reload this page.
changelog: Cutover to remove NEXT_CHANGELOG.md - #5831
Merged
Conversation
janniklasrosetemporarily deployed
to
test-trigger-is
July 3, 2026 16:16 — with 
GitHub Actions
Inactive
janniklasrosetemporarily deployed
to
test-trigger-is
July 3, 2026 16:16 — with GitHub Actions
Inactive
Collaborator
Integration test reportCommit: ff8914e
8 interesting tests: 4 SKIP, 2 RECOVERED, 2 flaky
Top 10 slowest tests (at least 2 minutes):
|
janniklasrosetemporarily deployed
to
test-trigger-is
July 10, 2026 11:26 — with GitHub Actions
Inactive
janniklasrosetemporarily deployed
to
test-trigger-is
July 10, 2026 11:26 — with GitHub Actions
Inactive
The .nextchanges/ system fully drives the release now (release_tagging.py renders CHANGELOG.md straight from fragments), so NEXT_CHANGELOG.md is no longer read by anything. Remove it, migrating its one pending v1.8.0 entry to a .nextchanges/ fragment (verified it renders identically). Repoint a stale NEXT_CHANGELOG.md reference in an acceptance test comment at CHANGELOG.md. Co-authored-by: Isaac
janniklasroseforce-pushed
the
janniklasrose/nextchangelog-cutover
branch
from
July 10, 2026 17:10
a014ca8 to
ea67c50Comparejanniklasrosetemporarily deployed
to
test-trigger-is
July 10, 2026 17:10 — with GitHub Actions
Inactive
janniklasrosetemporarily deployed
to
test-trigger-is
July 10, 2026 17:10 — with GitHub Actions
Inactive
| @@ -1,15 +0,0 @@ | |||
| # NEXT CHANGELOG | |||
| ## Release v1.8.0 | |||
ContributorAuthor
There was a problem hiding this comment.
note https://github.com/databricks/cli/blob/main/.nextchanges/version is already at 1.8.0 so no need for cutover
janniklasrose
marked this pull request as ready for review
July 10, 2026 17:12
bradleyjamrozik-origindigital pushed a commit
to Origin-Digital-LLC/databricks-cli
that referenced
this pull request
Jul 13, 2026
…t into files (databricks#5534) ## Changes - Added `.nextchanges/` scaffolding (one file per entry, grouped by section) - Release renders fragments straight into `CHANGELOG.md` via a repo-owned `internal/genkit/release_tagging.py` wrapper around the synced `tagging.py` - Release version tracked in `.nextchanges/version` (auto-bumped each release) - New `check-changelog` Taskfile target; `validate_nextchanges.py` validates fragment placement + the version file - Updated agent PR skill ## Why Prevent common merge conflicts on the file during busy/productive times, requiring manual action to rebase. Why not `merge=union` in .gitattributes? Easy quality of life for local, but unfortunately [not supported by GitHub](https://github.com/orgs/community/discussions/9288). ## Tests - e925f8d - add dummy entries into `.nextchanges/` (mixed `* ` / `- ` / no marker) - a339ab0 - simulate the release: render into `CHANGELOG.md` (blank line after each heading, markers normalized to ` * `), delete fragments, bump `version` - `validate_nextchanges.py` rejects bad entries (each exits 1): - misplaced fragment (unknown section dir) → `not in a known section directory` - empty fragment → `empty fragment` - missing `.nextchanges/version` → `missing; expected the next release version` - malformed version → `not a valid semver version` ## Rollout (follow-up) This PR already renders `.nextchanges/` directly into `CHANGELOG.md` at release. `NEXT_CHANGELOG.md` is intentionally left in the tree, now unused, to keep this PR focused. **Follow-up cutover PR:** databricks#5831 `git rm NEXT_CHANGELOG.md` once nothing references it. It's split out so this PR is easy to review and revert; the deletion is mechanical. _This pull request was written by Isaac, an AI coding agent._
janniklasrosetemporarily deployed
to
test-trigger-is
July 14, 2026 09:30 — with GitHub Actions
Inactive
janniklasrosetemporarily deployed
to
test-trigger-is
July 14, 2026 09:30 — with GitHub Actions
Inactive
janniklasrose
enabled auto-merge
July 14, 2026 09:31
pietern
approved these changes
Jul 14, 2026
eng-dev-ecosystem-bot
commented
Jul 14, 2026
Collaborator
Integration test reportCommit: 9b34ac4
37 interesting tests: 24 flaky, 6 FAIL, 4 RECOVERED, 2 SKIP, 1 KNOWN
Top 50 slowest tests (at least 2 minutes):
|
ronaldz-db pushed a commit
to ronaldz-db/cli
that referenced
this pull request
Jul 15, 2026
…sue databricks#4179 (databricks#5923) The fragment added by databricks#5831 linked the `env:` section changelog entry to the original issue (databricks#4179) rather than the PR that implemented the feature (databricks#5299). This includes both links.
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 freeto 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
NEXT_CHANGELOG.md— the.nextchanges/system fully drives the release now, so nothing reads it anymore..nextchanges/fragments (verified they render identically).NEXT_CHANGELOGreferences in theonboard-team-areaskill to.nextchanges/.Why
Follow-up cutover to #5534. That PR left
NEXT_CHANGELOG.mdin the tree (unused) to stay focused;release_tagging.pyalready rendersCHANGELOG.mdstraight from.nextchanges/fragments. This deletes the now-vestigial file and its last references.Tests
task check-changelogpasses (fragments +versionvalid).release_tagging.pyreads only.nextchanges/(fragments +version), neverNEXT_CHANGELOG.md, so the deletion changes no release behavior.NEXT_CHANGELOG.mdbody byte-for-byte.This pull request was written by Isaac, an AI coding agent.