Skip to content
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

Version Packages #4126

Merged
merged 1 commit into from
Oct 11, 2023
Merged

Version Packages #4126

merged 1 commit into from
Oct 11, 2023

Conversation

workers-devprod
Copy link
Contributor

@workers-devprod workers-devprod commented Oct 6, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

wrangler@3.12.0

Minor Changes

  • #4071 f880a009 Thanks @matthewdavidrodgers! - Support TailEvent messages in Tail sessions

    When tailing a tail worker, messages previously had a null event property. Following Add TraceEventInfo for TraceItem workerd#1248, these events have a valid event, specifying which scripts produced events that caused your tail worker to run.

    As part of rolling this out, we're filtering out tail events in the internal tail infrastructure, so we control when these new messages are forward to tail sessions, and can merge this freely.

    One idiosyncracy to note, however, is that tail workers always report an "OK" status, even if they run out of memory or throw. That is being tracked and worked on separately.

  • #2397 93833f04 Thanks @a-robinson! - feature: Support Queue consumer events in tail

    So that it's less confusing when tailing a worker that consumes events from a Queue.

Patch Changes

  • #2687 3077016f Thanks @jrf0110! - Fixes large Pages projects failing to complete direct upload due to expiring JWTs

    For projects which are slow to upload - either because of client bandwidth or large numbers of files and sizes - It's possible for the JWT to expire multiple times. Since our network request concurrency is set to 3, it's possible that each time the JWT expires we get 3 failed attempts. This can quickly exhaust our upload attempt count and cause the entire process to bail.

    This change makes it such that jwt refreshes do not count as a failed upload attempt.

  • #4069 f4d28918 Thanks @a-robinson! - Default new Hyperdrive configs for PostgreSQL databases to port 5432 if the port is not specified

create-cloudflare@2.4.1

Patch Changes

@workers-devprod workers-devprod requested review from a team as code owners October 6, 2023 11:13
@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2023

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6484668964/npm-package-wrangler-4126

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6484668964/npm-package-wrangler-4126

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6484668964/npm-package-wrangler-4126 dev path/to/script.js
Additional artifacts:
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6484668964/npm-package-cloudflare-pages-shared-4126

Note that these links will no longer work once the GitHub Actions artifact expires.


wrangler@3.12.0 includes the following runtime dependencies:

Package Constraint Resolved
miniflare 3.20231010.0 3.20231010.0
workerd 1.20231010.0 1.20231010.0
workerd --version 1.20231010.0 2023-10-10

|

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

@codecov
Copy link

codecov bot commented Oct 6, 2023

Codecov Report

Merging #4126 (d205dcf) into main (bfc9a3e) will increase coverage by 0.03%.
The diff coverage is n/a.

❗ Current head d205dcf differs from pull request most recent head 43a7a55. Consider uploading reports for the commit 43a7a55 to get more accurate results

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #4126      +/-   ##
==========================================
+ Coverage   75.38%   75.41%   +0.03%     
==========================================
  Files         223      223              
  Lines       12214    12214              
  Branches     3158     3158              
==========================================
+ Hits         9207     9211       +4     
+ Misses       3007     3003       -4     

see 3 files with indirect coverage changes

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 6 times, most recently from 6b66a75 to 2d6fb78 Compare October 10, 2023 17:11
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 4 times, most recently from 3094d64 to 7eab2af Compare October 11, 2023 13:42
@lrapoport-cf lrapoport-cf merged commit 763ecce into main Oct 11, 2023
40 checks passed
@lrapoport-cf lrapoport-cf deleted the changeset-release/main branch October 11, 2023 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants