[Docs Site] Load WARP releases into WARP changelog #19901
Closed
Conversation
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
KianNH
requested review from
a team,
GregBrimble,
WalshyDev,
haleycode,
kodster28,
kristianfreeman,
marciocloudflare,
maxvp,
pedrosousa and
ranbel
as code owners
github-actions
bot
assigned
GregBrimble,
haleycode,
kodster28,
kristianfreeman,
marciocloudflare,
maxvp,
pedrosousa,
WalshyDev and
ranbel
Contributor
|
Preview URL: https://47e4126b.preview.developers.cloudflare.com |
Member
Author
|
Postponing this work until we figure out how to merge release notes and changelogs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 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.
Summary
This loads WARP releases into the
entriesof the existingsrc/content/changelogs/warp.yaml.They will appear in the global changelog, global RSS feed,
/cloudflare-one/changelog/warp/and/cloudflare-one/changelog/warp/index.xml.The code is duplicated since all of the code in these areas is duplicated - we were going to tackle this in #19631 but shelved that work in favour of changelog-next.
This also fixes the duplication of
dateheaders inProductChangelog, so multiple releases for the same day (i.e one for Windows and one for macOS) do not cause 3 identical headings.