Cut over: remove NEXT_CHANGELOG.md#5831
Draft
janniklasrose wants to merge 1 commit into
Draft
Conversation
The .nextchanges/ system fully drives the release now, so NEXT_CHANGELOG.md is no longer read by anything (release_tagging.py renders CHANGELOG.md from .nextchanges/). Remove it, migrating its two pending v1.7.0 entries to .nextchanges/ fragments (verified they render identically). Update the onboard-team-area skill's remaining NEXT_CHANGELOG references to .nextchanges/. Co-authored-by: Isaac
janniklasrose
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
janniklasrose
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Collaborator
Integration test reportCommit: aa2146d
19 interesting tests: 15 SKIP, 4 RECOVERED
Top 5 slowest tests (at least 2 minutes):
|
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
2 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.Stacking
Stacked on top of #5534 (
janniklasrose/changelog-merge-conflicts). Merge that first; this PR's base should be retargeted tomainonce #5534 lands.This pull request was written by Isaac, an AI coding agent.