Repository navigation
CHANGELOG: Sort "unreleased" changes under their release versions - #980
Merged
Merged
Conversation
Each bullet under Unreleased was matched against the CHANGELOG shipped in every release tag, and moved under the lowest version whose chart contains it. Five bullets newer than v8.1.2687 stay under Unreleased. Amp-Thread-ID: https://ampcode.com/threads/T-01a16525-9761-7145-85e0-86c81f2f1ac8 Co-authored-by: Amp <amp@ampcode.com>
marcleblanc2
force-pushed
the
marc/changelog-release-headings
branch
from
October 29, 2026 22:13
d9cf38d to
ee1b286
Compare
marcleblanc2
changed the title
…eadings Same method as the sourcegraph chart: each bullet under Unreleased was matched against the CHANGELOG shipped in every release tag, and moved under the lowest version whose chart contains it. The two oldest bullets are in v5.3.9104, the oldest tag in the repo, so they shipped there or earlier. Nothing remains under Unreleased. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a189b8-62b4-7754-af9e-46f9d940d0c7
DaedalusG
approved these changes
Oct 29, 2026
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
sourcegraphchart CHANGELOG had 28 bullets under Unreleased, going back to changes that shipped in 6.1.0. This moves each bullet under the release it first shipped in; nothing is reworded.For each bullet I checked the
charts/sourcegraph/CHANGELOG.mdshipped in everyv*tag and took the lowest version containing it (cross-checked againstgit tag --containson the commit that added it; both methods agree):outbound-http-proxyexample,codeintel-dbPVC name fix,indexedSearch.readinessProbe/indexedSearch.livenessProbe,searcher.storageSizequantity parsing (all newer than v8.1.2687)grafana.initContainers,gitserver.storageAccessModes, graceful shutdown, syntect/searcher PDBs,DEPLOY_TYPE=helmextraContainersfix,searcher.autoCacheSize/dataPVC +replicasremovalreplicaCount, per-serviceimage.repositorysourcegraph-executorchartThe executor CHANGELOG had four bullets under Unreleased and no release headings at all. Same method, same result: nothing reworded.
network-policyexamplesecurityContextdeprecation insourcegraph-executor-k8s(not in v7.0.0 or v7.0.2178)sourcegraph-executor-k8schart, rename tosourcegraph-executor-dind(v5.3.9104 is the oldest tag in the repo, so these shipped there or earlier)Note the four oldest bullets predate the current
mainhistory (it re-roots at c7b92eb); their versions come from the v6.x tags, which still carry the old history.Checklist
Test plan
Docs only. Verified the set of bullet lines in both files is byte-identical to
main(only headings added).markdownlint-cli2reports the same 65 pre-existing findings on thesourcegraphCHANGELOG before and after, and 7 → 5 on the executor one (blank lines around the new headings).