-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Update edgeworker release notes for last week's releases. #20555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Howdy and thanks for contributing to our repo. 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. |
| entries: | ||
| - publish_date: "2025-02-28" | ||
| description: |- | ||
| - The new `queue_consumer_no_wait_for_wait_until` compatibility flag changes behaviour for queue consumers, changing their behavior such that (A) `waitUntil` promises do not need to complete before a queue consumer invocation can be considered complete, and (B) `waitUntil` promises failing do not cause the invocation as a whole to fail. Neither of these have been the case previously, allowing long-running or errant `waitUntil` tasks to (usually unintentionally) slow down or prevent successful message consumption. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@a-robinson I made a couple of edits here e.g. adding the name of the compatibility flag itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Although would it be too hard to delay this until the next batch of release notes? A bug was found in the flag and a fix was just merged last night, and I wouldn't recommend anyone use it until that fix has rolled out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although on a more fun / less important note I like the different spellings of behaviour and behavior just a few words apart from each other :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. I'll remove this one for now and punt it to the next release notes cc @harrishancock
|
Preview URL: https://88a4fb5d.preview.developers.cloudflare.com |
ed9b1a6 to
88a4fb5
Compare
Summary
Screenshots (optional)
Documentation checklist