chore: sync the 2.16.0 changelog cut back to develop - #768
Merged
Conversation
Release: develop → main (v2.16.0)
docs: cut changelog for v2.16.0
The release workflow promotes [Unreleased] into a version section on main, and that commit has to come back here or the branches drift -- which is what made the release PR conflict earlier today, three releases running. This is a real merge, not a copy of the content, so main is an ancestor of develop and the next release merge is a fast-forward. Also corrects one sentence in the promoted entry: it claimed the update check is the only request PoracleWeb makes outside your own network. It is not. MasterDataService fetches the Pokemon master data from raw.githubusercontent.com on any visit. The documentation verification pass caught that and the docs were fixed; the changelog entry was not, and the promotion carried it into a released section. Claude-Session: https://claude.ai/code/session_01Nah4N2sGFs1TU2t7DXfKzJ
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
1 participant
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.
Two things in one, both consequences of cutting v2.16.0.
The sync.
release-changelog.ymlpromoted[Unreleased]into## [2.16.0]onmain(#767). That commit has to come back todevelopor the branches drift — which is exactly what made #755 conflict earlier today, and it had been drifting for three releases. This is a real merge with both parents, somainstays an ancestor ofdevelopand the next release merge is a fast-forward rather than a conflict.The correction. The promoted entry claimed the update check "is the only request PoracleWeb makes outside your own network". It isn't —
MasterDataServicefetches the Pokemon master data from raw.githubusercontent.com on any visit. The documentation verification pass caught this and the docs were corrected in #763; the changelog entry it came from wasn't, so #767 wrote the claim into a released section. I tried to fix it on #767's branch but it was already queued and locked, so it lands here.mainwill still carry the wrong sentence in its 2.16.0 section until the next release merge brings this over. The published release notes on GitHub don't repeat the claim, and the docs site is already correct.https://claude.ai/code/session_01Nah4N2sGFs1TU2t7DXfKzJ