@hunt-labs/bytekit-sdk 0.7.2 → 0.7.4

package/CHANGELOG.md

@@ -10,6 +10,42 @@ today, see [README.md](./README.md), which remains the authoritative usage guide
 
 ## [Unreleased]
 
+## [0.7.4] - 2026-08-19
+
+### Changed
+
+- **`gen:version` no longer runs as part of `build`** (#3144). `scripts/gen-version.ts` writes
+  `src/version.ts`, a _tracked_ source file, and it was chained into the `build` script. That made
+  a build silently rewrite committed source whenever the file disagreed with the manifest: local
+  runs went green on a tree CI could fail, the resulting ` M src/version.ts` was indistinguishable
+  from routine build noise, and in CI the outcome depended on whether Turbo's build cache hit
+  (restoring `dist/**` without re-running the generator) or missed. `build` now starts at
+  `rm -rf dist ...`, so building this package touches nothing tracked. This changes `prepack` /
+  `prepublishOnly` behavior too: both call `build`, so the publish path now reads the committed
+  `src/version.ts` rather than regenerating it, and the committed value is what ships.
+- **New `gen:version-check` script**, `pnpm gen:version && git diff --exit-code src/version.ts`,
+  mirroring the existing `gen:types-check` in the same manifest. It runs in `.woodpecker/ci.yaml`'s
+  `types-drift` step, so a manifest bump without the matching `src/version.ts` regeneration now
+  fails a named PR check instead of reaching `staging`. `src/__tests__/version-parity.test.ts`
+  stays in place as the in-suite assertion; the gate is what makes its failure reachable before
+  merge rather than after.
+
+No runtime or type changes. `SDK_VERSION` and the `X-ByteKit-Client: sdk_ts/<version>` affix
+behave exactly as before.
+
+## [0.7.3] - 2026-08-18
+
+### Changed
+
+- **`XFetchContentLength`'s description no longer calls the header a wire-byte count** (#3133).
+  `X-Fetch-Content-Length` is the byte length of the response body actually served: on a
+  passthrough `/v1/fetch` (no `format`) that is the relayed upstream payload, so it does equal
+  the upstream wire bytes — but with `format=html` or `format=markdown` the gateway overwrites
+  it with the transformed document's length, which is typically far smaller than what is billed.
+  The old description therefore read as a billing discrepancy on every transform request. Billing
+  is unchanged and has always used the upstream compressed wire bytes reported by `X-Raw-Bytes` /
+  `X-Billable-Bytes`. Generated-type comments only; no type or runtime behavior changes.
+
 ## [0.7.2] - 2026-08-17
 
 ### Changed
@@ -521,6 +557,8 @@ against 0.1.0 — read each one before upgrading.
   `@rapidcrawl/sdk` name.
 
 [Unreleased]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
+[0.7.4]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
+[0.7.3]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
 [0.7.2]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
 [0.7.1]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
 [0.7.0]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript

package/dist/generated/api.d.ts

@@ -2626,7 +2626,14 @@ export interface components {
          */
         XFetchStatus: "completed";
         XFetchURL: string;
-        /** @description Wire byte count (integer as string). */
+        /**
+         * @description Byte length of the response body served on this request (integer as string) — NOT the
+         *     billing basis. On a passthrough request (no `format`) the body is the relayed upstream
+         *     payload, so this equals the upstream wire byte count. With `format=html` or
+         *     `format=markdown` the body is the transformed document, so this is the transformed byte
+         *     count and is typically far smaller than what is billed. Billing always reads the upstream
+         *     compressed wire bytes from `X-Raw-Bytes` / `X-Billable-Bytes`, on every path.
+         */
         XFetchContentLength: string;
         XFetchCreditsCharged: string;
         XFetchDurationMs: string;

package/dist/version.d.ts

@@ -5,4 +5,4 @@
  * outbound request carries — see the emit site in `client.ts`. The header name is spelled
  * only there, so issue #2905's pre-merge gate 1 counts exactly one occurrence in `src/`.
  */
-export declare const SDK_VERSION = "0.7.2";
+export declare const SDK_VERSION = "0.7.4";

package/dist/version.js

@@ -9,4 +9,4 @@
  * outbound request carries — see the emit site in `client.ts`. The header name is spelled
  * only there, so issue #2905's pre-merge gate 1 counts exactly one occurrence in `src/`.
  */
-export const SDK_VERSION = '0.7.2';
+export const SDK_VERSION = '0.7.4';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hunt-labs/bytekit-sdk",
-  "version": "0.7.2",
+  "version": "0.7.4",
   "description": "Official TypeScript SDK for the ByteKit API",
   "license": "MIT",
   "type": "module",
@@ -48,10 +48,11 @@
     "url": "https://bytekit.com/contact"
   },
   "scripts": {
-    "build": "pnpm gen:version && rm -rf dist tsconfig.tsbuildinfo tsconfig.build.tsbuildinfo && tsc -p tsconfig.build.json && mkdir -p dist/generated && cp src/generated/api.d.ts dist/generated/api.d.ts",
+    "build": "rm -rf dist tsconfig.tsbuildinfo tsconfig.build.tsbuildinfo && tsc -p tsconfig.build.json && mkdir -p dist/generated && cp src/generated/api.d.ts dist/generated/api.d.ts",
     "gen:types": "openapi-typescript ../../docs/api/openapi.yaml -o src/generated/api.d.ts",
     "gen:version": "tsx scripts/gen-version.ts",
     "gen:types-check": "pnpm gen:types && git diff --exit-code src/generated/api.d.ts",
+    "gen:version-check": "pnpm gen:version && git diff --exit-code src/version.ts",
     "generate:docs": "tsx scripts/generate-docs.ts",
     "typecheck": "tsc --noEmit",
     "test": "vitest run"