[Release notes] Stop pulling Wrangler release notes from GitHub API #21046
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryDeprecation of Wrangler release notes in favor of summarized changelog entries.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add What is Hyperlint?Hyperlint is an AI agent that helps you write, edit, and maintain your documentation. Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation. |
kodster28
changed the title
|
Preview URL: https://9d586814.preview.developers.cloudflare.com Files with changes (up to 15)
|
github-actions
bot
assigned
GregBrimble,
KianNH,
pedrosousa,
WalshyDev,
irvinebroque,
haleycode and
kristianfreeman
kodster28
requested review from
a team,
GregBrimble,
KianNH,
WalshyDev,
haleycode,
irvinebroque,
kristianfreeman and
pedrosousa
as code owners
…21046) * [Release notes] Deprecate wrangler release notes * remove unused imports * Added redirect
8 participants
Summary
With the Wrangler team more consistently writing up summarized changelog entries, think it's time to re-think having the Wrangler release notes ported into docs.
The reason why is b/c the GitHub API usually ends up failing about
8 buildsa day as a result of rate limiting. Given that the information is also already clearly available in GitHub (with an RSS feed there too), there doesn't appear to be much added value in also surfacing them in docs.Theoretically, I suppose we could rewrite the component.... but there's a lot of other investment that needs to go into other things changelog so I'd rather spend the time there.
cc: @GregBrimble / @mikenomitch, fyi that this is an option we're considering. Open to having a convo if I'm missing pieces related to ☝️ .
Additional context on timing
This has been more painful recently and -- with Dev Week coming up -- we don't want to be blocking any docs previews or publishes from going live.