bun-types 1.2.0-canary.20250124T140542 → 1.2.0

package/bun.d.ts

@@ -1468,28 +1468,6 @@ declare module "bun" {
 		 */
 		type?: string;
 
-		/**
-		 * By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects.
-		 *
-		 * @example
-		 *    // Setting explicit Storage class
-		 *     const file = s3("my-file.json", {
-		 *       storageClass: "STANDARD_IA"
-		 *     });
-		 */
-		storageClass?:
-			| "STANDARD"
-			| "DEEP_ARCHIVE"
-			| "EXPRESS_ONEZONE"
-			| "GLACIER"
-			| "GLACIER_IR"
-			| "INTELLIGENT_TIERING"
-			| "ONEZONE_IA"
-			| "OUTPOSTS"
-			| "REDUCED_REDUNDANCY"
-			| "SNOW"
-			| "STANDARD_IA";
-
 		/**
 		 * @deprecated The size of the internal buffer in bytes. Defaults to 5 MiB. use `partSize` and `queueSize` instead.
 		 */

package/docs/api/fetch.md

@@ -195,7 +195,7 @@ This will print the request and response headers to your terminal:
 ```sh
 [fetch] > HTTP/1.1 GET http://example.com/
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.0-canary.20250124T140542
+[fetch] > User-Agent: Bun/bun-v1.2.0
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/api/s3.md

@@ -171,24 +171,11 @@ When your production service needs to let users upload files to your server, it'
 
 To facilitate this, you can presign URLs for S3 files. This generates a URL with a signature that allows a user to securely upload that specific file to S3, without exposing your credentials or granting them unnecessary access to your bucket.
 
-The default behaviour is to generate a `GET` URL that expires in 24 hours. Bun attempts to infer the content type from the file extension. If inference is not possible, it will default to `application/octet-stream`.
-
 ```ts
 import { s3 } from "bun";
 
 // Generate a presigned URL that expires in 24 hours (default)
-const download = s3.presign("my-file.txt"); // GET, text/plain, expires in 24 hours
-
-const upload = s3.presign("my-file", {
-  expiresIn: 3600, // 1 hour
-  method: 'PUT',
-  type: 'application/json', // No extension for inferring, so we can specify the content type to be JSON
-});
-
-// You can call .presign() if on a file reference, but avoid doing so
-// unless you already have a reference (to avoid memory usage).
-const myFile = s3.file("my-file.txt");
-const presignedFile = myFile.presign({
+const url = s3.presign("my-file.txt", {
   expiresIn: 3600, // 1 hour
 });
 ```

package/docs/api/spawn.md

@@ -110,7 +110,7 @@ You can read results from the subprocess via the `stdout` and `stderr` propertie
 ```ts
 const proc = Bun.spawn(["bun", "--version"]);
 const text = await new Response(proc.stdout).text();
-console.log(text); // => "1.2.0-canary.20250124T140542"
+console.log(text); // => "bun-v1.2.0"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

package/docs/cli/publish.md

@@ -7,7 +7,7 @@ Use `bun publish` to publish a package to the npm registry.
 $ bun publish
 
 ## Output
-bun publish v1.2.0-canary.20250124T140542 (ca7428e9)
+bun publish vbun-v1.2.0 (ca7428e9)
 
 packed 203B package.json
 packed 224B README.md

package/docs/runtime/debugger.md

@@ -124,11 +124,11 @@ await fetch("https://example.com", {
 This prints the `fetch` request as a single-line `curl` command to let you copy-paste into your terminal to replicate the request.
 
 ```sh
-[fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.0-canary.20250124T140542" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
+[fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/bun-v1.2.0" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
 [fetch] > HTTP/1.1 POST https://example.com/
 [fetch] > content-type: application/json
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.0-canary.20250124T140542
+[fetch] > User-Agent: Bun/bun-v1.2.0
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br
@@ -170,7 +170,7 @@ This prints the following to the console:
 [fetch] > HTTP/1.1 POST https://example.com/
 [fetch] > content-type: application/json
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.0-canary.20250124T140542
+[fetch] > User-Agent: Bun/bun-v1.2.0
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/test/dom.md

@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
 
 ```bash
 $ bun test
-bun test v1.2.0-canary.20250124T140542
+bun test vbun-v1.2.0
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-	"version": "1.2.0-canary.20250124T140542",
+	"version": "1.2.0",
 	"name": "bun-types",
 	"license": "MIT",
 	"main": "",