@effected/github 0.14.0 → 0.15.0

package/internal/headers.js

@@ -1,14 +1,4 @@
 //#region src/internal/headers.ts
-/**
-* Reading GitHub's response headers.
-*
-* @remarks
-* octokit hands headers back as a plain object whose values may be `string`,
-* `number` or absent depending on the fetch implementation, so every read here
-* is defensive about both. Header names are already lowercased by octokit.
-*
-* @internal
-*/
 /** A header's value as a string, when it is present and non-empty. */
 const headerString = (headers, name) => {
 	const value = headers?.[name];

package/internal/octokit.js

@@ -21,11 +21,9 @@ const SILENT_LOG = {
 * distinction an app JWT and an installation token need, so the App path
 * requires no separate auth strategy.
 *
-* `log` is silenced. The package this replaces installed
-* `plugin-request-log` and then rerouted every line of it into an Actions
-* `::debug::` workflow command, which is how GitHub Actions knowledge ended up
-* inside a GitHub API client. Here retries log through `Effect.logDebug`, and an
-* application maps Effect's logs to whatever its runtime wants.
+* `log` is silenced. Retries log through `Effect.logDebug`, and an application
+* maps Effect's logs to whatever its runtime wants, so no GitHub Actions
+* knowledge lives in this client.
 */
 const makeOctokit = (options) => new Octokit({
 	...options.token !== void 0 ? { auth: Redacted.value(options.token) } : {},
@@ -38,12 +36,8 @@ const makeOctokit = (options) => new Octokit({
 * Build a transport over a freshly constructed octokit instance.
 *
 * @remarks
-* The rate-limit cell lives here, in the closure of the layer that writes it.
-* The package this replaces made it an optional shared `Ref` **service** that
-* the writer and the reader both resolved through `Effect.serviceOption`, so an
-* application that forgot to provide it got two private cells, a limiter that
-* never saw the client's headers, and no error, warning or type signal saying
-* so.
+* The rate-limit cell lives here, in the closure of the layer that writes it,
+* so the writer and the reader can never see different cells.
 */
 const makeTransport = (options) => Effect.gen(function* () {
 	const octokit = makeOctokit(options);

package/internal/paginate.js

@@ -8,10 +8,7 @@ import { Effect, Option, Stream } from "effect";
 * **This is the only pagination implementation in the package**, and it is why
 * the fixture double cannot drift from the live client: both build a
 * `PageSource` and hand it here, so `maxPages` and item flattening have exactly
-* one behavior. The package this replaces had a live loop that honored
-* `maxPages` and a test double whose equivalent parameters were named
-* `_options` and ignored — which made every truncation path structurally
-* untestable.
+* one behavior.
 *
 * `maxPages` bounds **requests, not items**: the walk stops issuing them rather
 * than fetching everything and slicing.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/github",
-	"version": "0.14.0",
+	"version": "0.15.0",
 	"private": false,
 	"description": "Typed GitHub REST and GraphQL services over the octokit core request surface, with app auth and resource helpers.",
 	"keywords": [
@@ -38,8 +38,8 @@
 		"./package.json": "./package.json"
 	},
 	"dependencies": {
-		"@effected/github-references": "^0.6.0",
-		"@effected/semver": "^0.10.0",
+		"@effected/github-references": "^0.7.0",
+		"@effected/semver": "^0.11.0",
 		"@octokit/core": "^7.0.6",
 		"@octokit/plugin-paginate-rest": "^15.0.0",
 		"@octokit/types": "^18.0.0",
@@ -48,7 +48,7 @@
 		"universal-github-app-jwt": "^2.2.2"
 	},
 	"peerDependencies": {
-		"effect": "4.0.0-rc.118"
+		"effect": "^4.0.0"
 	},
 	"engines": {
 		"node": ">=24.11.0"