[pull] main from cloudflare:main

.changeset/README.md

@@ -1,6 +1,7 @@
 # Changesets
 
 Every non-trivial change to the project - those that should appear in the changelog - must be captured in a "changeset".
+
 We use the [`changesets`](https://github.com/changesets/changesets/blob/main/README.md) tool for creating changesets, publishing versions and updating the changelog.
 
 ## Creating a Changeset
@@ -52,9 +53,7 @@ Add `wrangler d1 export` command for exporting D1 databases to SQL files
 
 You can now export your D1 database to a local SQL file:
 
-` ` `bash
-wrangler d1 export my-database --output backup.sql
-` ` `
+`wrangler d1 export my-database --output backup.sql`
 
 This is useful for creating backups or migrating data between databases.
 ```
@@ -68,8 +67,7 @@ For a bug fix (patch):
 
 Fix `wrangler dev` failing to start when `wrangler.toml` contains Unicode characters
 
-Previously, projects with non-ASCII characters in configuration values would fail with
-"Invalid UTF-8 sequence". This is now handled correctly.
+Previously, projects with non-ASCII characters in configuration values would fail with "Invalid UTF-8 sequence". This is now handled correctly.
 ```
 
 ### Bad Examples (avoid these)
@@ -124,6 +122,5 @@ Here's a complete example of a patch changeset file:
 
 Replace the word "publish" with "deploy" everywhere
 
-We should be consistent with the word that describes how we get a worker to the edge.
-The command is `deploy`, so let's use that everywhere.
+We should be consistent with the word that describes how we get a worker to the edge. The command is `deploy`, so let's use that everywhere.
 ```

.github/workflows/triage-issue.yml

@@ -133,7 +133,7 @@ jobs:
             }')
 
           # POST to dashboard API
-          HTTP_STATUS=$(curl -L -s -o response.json -w "%{http_code}" \
+          HTTP_STATUS=$(curl -L --post302 -s -o response.json -w "%{http_code}" \
             -X POST "${DASHBOARD_URL}/api/report/${ISSUE}" \
             -H "Content-Type: application/json" \
             -H "CF-Access-Client-Id: ${CF_ACCESS_CLIENT_ID}" \

.prettierrc

@@ -47,6 +47,12 @@
 				"trailingComma": "all",
 				"plugins": []
 			}
+		},
+		{
+			"files": ".changeset/*.md",
+			"options": {
+				"proseWrap": "never"
+			}
 		}
 	]
 }

packages/wrangler/README.md

@@ -54,24 +54,10 @@ For more detailed information about configuration, refer to the [documentation](
 
 ## Commands
 
-### Workers
+The `wrangler` CLI offers various commands, the most popular being:
 
-#### `wrangler dev`
+- `wrangler dev` to start a local development server, with live reloading and devtools.
 
-Start a local development server, with live reloading and devtools.
+- `wrangler deploy` to deploy a Worker to the Cloudflare's global network.
 
-#### `wrangler deploy`
-
-Publish the given script to Cloudflare's global network.
-
-For more commands and options, refer to the [documentation](https://developers.cloudflare.com/workers/wrangler/commands/).
-
-### Pages
-
-#### `wrangler pages dev [directory]`
-
-Serves a static build asset directory.
-
-Builds and runs functions from a `./functions` directory or uses a `_worker.js` file inside the static build asset directory.
-
-For more commands and options, refer to the [documentation](https://developers.cloudflare.com/pages/platform/functions#develop-and-preview-locally) or run `wrangler pages dev --help`.
+There are many more commands and options available, for a full list refer to the [official Cloudflare documentation](https://developers.cloudflare.com/workers/wrangler/commands/).