Skip to content

Commit d57b293

Browse files
authored
Merge branch 'production' into kian/PCX-15576
2 parents 116e8a2 + 4c41b6f commit d57b293

File tree

100 files changed

+1923
-443
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

100 files changed

+1923
-443
lines changed

package-lock.json

Lines changed: 17 additions & 17 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,11 +39,11 @@
3939
"@codingheads/sticky-header": "1.0.2",
4040
"@expressive-code/plugin-collapsible-sections": "0.40.1",
4141
"@iarna/toml": "2.2.5",
42-
"@iconify-json/material-symbols": "1.2.12",
42+
"@iconify-json/material-symbols": "1.2.13",
4343
"@stoplight/json-schema-tree": "4.0.0",
4444
"@types/hast": "3.0.4",
4545
"@types/he": "1.2.3",
46-
"@types/node": "22.10.7",
46+
"@types/node": "22.12.0",
4747
"@types/react": "19.0.7",
4848
"@types/react-dom": "19.0.3",
4949
"@typescript-eslint/parser": "8.21.0",

public/_redirects

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -290,7 +290,7 @@
290290
/d1/reference/client-api/ /d1/worker-api/ 301
291291
/d1/reference/environments/ /d1/configuration/environments/ 301
292292
/d1/reference/metrics-analytics/ /d1/observability/metrics-analytics/ 301
293-
/d1/reference/wrangler-commands/ / /d1/wrangler-commands/ 301
293+
/d1/reference/wrangler-commands/ /d1/wrangler-commands/ 301
294294
/d1/how-to/ /d1/best-practices/ 301
295295
/d1/how-to/query-databases/ /d1/best-practices/query-d1/ 301
296296
/d1/how-to/using-indexes/ /d1/best-practices/use-indexes/ 301
@@ -399,6 +399,7 @@
399399
/durable-objects/api/transactional-storage-api/ /durable-objects/api/storage-api/ 301
400400
/durable-objects/platform/changelog/ /durable-objects/changelog/ 301
401401
/durable-objects/glossary/ /durable-objects/reference/glossary/ 301
402+
/durable-objects/get-started/walkthrough/ /durable-objects/get-started/tutorial/ 301
402403

403404
# email-routing
404405
/email-routing/enable-email-routing/ /email-routing/get-started/enable-email-routing/ 301

public/workers-ai-notebooks/cloudflare-workers-ai.ipynb

Lines changed: 32 additions & 26 deletions
Large diffs are not rendered by default.
9.95 KB
Loading
17.9 KB
Loading
181 KB
Loading
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
title: Up to 10x faster cached queries for Hyperdrive
3+
description: Hyperdrive now caches queries in all Cloudflare locations decreasing cache hit latency by up to 90%
4+
products:
5+
- hyperdrive
6+
date: 2024-12-11T18:00:00Z
7+
---
8+
9+
Hyperdrive now caches queries in all Cloudflare locations, decreasing cache hit latency by up to 90%.
10+
11+
When you make a query to your database and Hyperdrive has cached the query results, Hyperdrive will now return the results from the nearest cache. By caching data closer to your users, the latency for cache hits reduces by up to 90%.
12+
13+
This reduction in cache hit latency is reflected in a reduction of the session duration for all queries (cached and uncached) from Cloudflare Workers to Hyperdrive, as illustrated below.
14+
15+
![Hyperdrive edge caching improves average session duration for database queries](~/assets/images/hyperdrive/changelog/hyperdrive-edge-caching-metrics.png)
16+
17+
_P50, P75, and P90 Hyperdrive session latency for all client connection sessions (both cached and uncached queries) for Hyperdrive configurations with caching enabled during the rollout period._
18+
19+
This performance improvement is applied to all new and existing Hyperdrive configurations that have caching enabled.
20+
21+
For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/configuration/how-hyperdrive-works/#query-caching).
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Increased Workflows limits and improved instance queueing.
3+
description: More steps per Workflow + pause/resume now supported
4+
products:
5+
- workflows
6+
date: 2025-01-15
7+
---
8+
9+
[Workflows](/workflows/) (beta) now allows you to define up to 1024 [steps](/workflows/build/workers-api/#workflowstep). `sleep` steps do not count against this limit.
10+
11+
We've also added:
12+
13+
* `instanceId` as property to the [`WorkflowEvent`](/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance
14+
* Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state.
15+
* Support for [`pause` and `resume`](/workflows/build/workers-api/#pause) for Workflow instances in a queued state.
16+
17+
We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks.
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: AI Gateway Introduces New Worker Binding Methods
3+
description: New Worker binding methods, enhancing integration capabilities for developers.
4+
products:
5+
- ai-gateway
6+
date: 2025-01-30T14:00:00Z
7+
---
8+
9+
We have released new [Workers bindings API methods](/ai-gateway/integrations/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate.
10+
11+
To add an AI binding to your Worker, include the following in your `wrangler.toml` or `wrangler.json` file:
12+
13+
![Add an AI binding to your Worker.](~/assets/images/ai-gateway/add-binding.png)
14+
15+
With the new AI Gateway binding methods, you can now:
16+
17+
- Send feedback and update metadata with `patchLog`.
18+
- Retrieve detailed log information using `getLog`.
19+
- Execute [universal requests](/ai-gateway/providers/universal/) to any AI Gateway provider with `run`.
20+
21+
For example, to send feedback and update metadata using `patchLog`:
22+
23+
![Send feedback and update metadata using patchLog:](~/assets/images/ai-gateway/send-feedback.png)

0 commit comments

Comments
 (0)