fix(deps): update all dependencies by renovate[bot] · Pull Request #20 · ProverCoderAI/openapi-effect

renovate · 2026-02-21T13:44:04Z

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`^2.4.4` → `^2.6.6`	devDependencies	minor
@changesets/changelog-github (source)	`^0.5.2` → `^1.0.1`	devDependencies	major
@changesets/cli (source)	`^2.29.8` → `^3.0.3`	devDependencies	major
@eslint-community/eslint-plugin-eslint-comments	`^4.6.0` → `^4.8.1`	devDependencies	minor
@eslint/compat (source)	`2.0.2` → `2.1.1`	devDependencies	minor
@eslint/eslintrc	`3.3.3` → `3.3.7`	devDependencies	patch
@types/node (source)	`^24.10.13` → `^26.6.6`	devDependencies	major
@typescript-eslint/eslint-plugin (source)	`^8.56.0` → `^8.72.2`	devDependencies	minor
@typescript-eslint/parser (source)	`^8.56.0` → `^8.72.2`	devDependencies	minor
@vitest/coverage-v8 (source)	`^4.0.18` → `^5.1.0`	devDependencies	major
@vitest/eslint-plugin	`^1.6.9` → `^1.6.28`	devDependencies	patch
actions/checkout	`v6` → `v7`	action	major
actions/setup-node	`v6` → `v7`	action	major
actions/upload-artifact	`v6` → `v7`	action	major
effect (source)	`^3.19.18` → `^4.1.3`	dependencies	major
eslint (source)	`^10.0.1` → `^10.14.0`	devDependencies	minor
eslint-import-resolver-typescript	`^4.4.4` → `^4.4.5`	devDependencies	patch
eslint-plugin-simple-import-sort	`^12.1.1` → `^14.0.0`	devDependencies	major
eslint-plugin-sonarjs (source)	`^4.0.0` → `^4.2.2`	devDependencies	minor
eslint-plugin-unicorn	`^63.0.0` → `^79.0.0`	devDependencies	major
globals	`^17.3.0` → `^17.14.0`	devDependencies	minor
jscpd (source)	`^4.0.8` → `^5.4.3`	devDependencies	major
node	`24.13.1` → `26.13.0`	uses-with	major
pnpm (source)	`10.30.1` → `12.18.0`	packageManager	major
pnpm/action-setup	`v4` → `v6`	action	major
pnpm/action-setup	`v3` → `v6`	action	major
typescript (source)	`^5.9.3` → `^7.0.2`	devDependencies	major
typescript-eslint (source)	`^8.56.0` → `^8.72.2`	devDependencies	minor
vite (source)	`^7.3.1` → `^8.3.7`	devDependencies	major
vitest (source)	`^4.0.18` → `^5.1.0`	devDependencies	major

cc @skulidropek

Release Notes

biomejs/biome (@biomejs/biome)

`v2.6.6`

Compare Source

Patch Changes

#12887 da0422e Thanks @dyc3! - Added the new nursery rule noArrayMethodsOnArguments. It reports calls to array methods on the arguments object, which isn't an array, so these calls throw a TypeError when the code runs.
```
function sum() {
  return arguments.reduce((total, value) => total + value, 0);
}
```
#12877 cd9e10f Thanks @dyc3! - Added the nursery rule noConstantComparisons, which reports && and || conditions that can never be true, are always true, or contain a check with no effect.
```
if (statusCode <= 400 && statusCode > 500) {}
```
#12876 a7c9586 Thanks @dyc3! - Added the nursery rule noErasingOperation, which disallows operations with 0 that always result in zero: multiplying by 0, a bitwise AND with 0, and dividing 0 by a number. The other value in these operations has no effect on the result, which usually means the code has a mistake.
```
const total = price * 0;
```
#12841 e954f55 Thanks @dyc3! - Added the nursery rule noNegatedArrayPredicate, which reports negated calls to Array#some() and Array#every() and suggests moving the negation into the callback function.
```
// Invalid: use `array.every((item) => !isUnicorn(item))` instead.
const isMissing = !array.some((item) => isUnicorn(item));
```
#12888 15039f7 Thanks @dyc3! - Added the new nursery rule noNumberArgumentOutOfRange, which reports number literal arguments of toString(), toFixed(), toExponential() and toPrecision() that are outside the range the method accepts. These calls throw a RangeError at runtime.
```
value.toString(64);
```
#12889 1cd7520 Thanks @dyc3! - Added the nursery rule noSharedBranchCode, which reports code that is repeated at the start or end of every branch of an if statement. That code runs no matter which branch is taken, so it can be moved before or after the if statement.
```
if (condition) {
  doSomething();
  cleanup();
} else {
  doSomethingElse();
  cleanup();
}
```
#12842 d47fcfd Thanks @dyc3! - Added the new nursery rule noSubtractionComparison, which reports subtracting two values only to compare the difference with 0, and suggests comparing the values directly.
```
if (a - b > 0) {}
```
#12866 7c1cd5f Thanks @dyc3! - Added the nursery rule noSvelteIgnoredUnsubscribe, which reports calls to a store's subscribe() method when the returned function is ignored. Without that function, the subscription can never be stopped, which causes a memory leak.
```
<script>
  import { count } from "./stores.js";

  count.subscribe((value) => console.log(value));
</script>
```
#12890 6b73fcf Thanks @dyc3! - Added the new nursery rule noUninvokedArrayCallback, which reports array methods such as map() and forEach() called with a callback on an array that only has empty slots. The callback never runs in this case.
```
const list = new Array(5).map(() => createElement());
```
#12886 3bb18d8 Thanks @dyc3! - Added the nursery rule useNextScriptForGoogleAnalytics, which reports <script> elements that load Google Analytics or Google Tag Manager. Use the GoogleAnalytics and GoogleTagManager components from @next/third-parties/google instead, which load these scripts after the page becomes interactive.
```
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XYZ" />
```
The rule belongs to the next domain.
#12309 0538e30 Thanks @dyc3! - Added the new nursery rule usePackageJsonCpu, which reports package.json files that have no cpu field. The cpu field lists the processor types that the package supports.

The following package.json file satisfies the rule:
```
{
  "name": "my-package",
  "version": "1.0.0",
  "cpu": ["x64", "arm64"]
}
```
#12310 191111d Thanks @dyc3! - Added the nursery rule usePackageJsonEngines, which reports package.json files that have no engines field.

A package.json passes the rule once it declares the field:
```
{
  "name": "my-package",
  "engines": {
    "node": ">=20"
  }
}
```
#12986 cc929af Thanks @dyc3! - Fixed #12954, where configuring rules in groups with more than 256 rules could enable or disable the wrong rule.
#12931 fe9248e Thanks @dyc3! - Improved the performance of linting. Each lint pass now spends less time stepping over syntax nodes that no enabled rule looks at.
#12969 22d27e8 Thanks @vibbix! - Improved the performance of CSS linting. Rules that compare selectors, such as noDescendingSpecificity and noDuplicateSelectors, now make fewer memory allocations.
#12973 5a06df5 Thanks @vibbix! - Fixed useGenericFontNames reporting font-family inside @font-palette-values. There, font-family names the font families the palette applies to, so it doesn't take a generic family.
```
@font-palette-values --palette {
  font-family: Bixa;
  override-colors: 0 red;
}
```
#12930 ce71284 Thanks @dyc3! - Fixed #12073: useExhaustiveSwitchCases now reports non-exhaustive switches over values read from for...of loops over Array.prototype.entries(), Map, and Set, and over properties of array elements indexed by a number variable.

noMisusedPromises now also reports Promise-returning callbacks passed to array methods such as find and every.
#12983 2987b54 Thanks @ashokram-si! - Fixed #12957: Biome now correctly parses SCSS negative interpolation list items as separate values instead of an invalid subtraction operator.
```
-margin: -#{$s} - #{$s} - #{$s} auto;
+margin: -#{$s} -#{$s} -#{$s} auto;
```

`v2.6.5`

Compare Source

Patch Changes

#12755 bbc4887 Thanks @dyc3! - Added the new nursery rule noArrayForEach, which reports forEach() calls that can be written as for...of loops. Values known not to be arrays, such as a Map or a Set, are ignored.
```
array.forEach((element) => {
	bar(element);
});
```
#12777 ba692e4 Thanks @dyc3! - Added the new nursery rule noAwaitInPromiseMethods, which reports await inside the array passed to Promise.all(), Promise.allSettled(), Promise.any(), or Promise.race(). The await pauses the code before the method is called, so the promises no longer run at the same time.
```
Promise.all([await promise, anotherPromise]);
```
#12765 af84fb4 Thanks @dyc3! - Added the new nursery rule noChainedComparison, which reports comparisons chained like a < b < c or a === b === c. JavaScript compares a with b first, and then compares the resulting true or false with c, so 3 > 2 > 1 is false.
```
if (a < b < c) {}
```
#12547 0a2073d Thanks @dyc3! - Added the nursery rule noDynamicDelete, which disallows using delete with a property name that is computed at runtime. Fixed property names written as string or number literals are allowed.
```
delete container[name];
```
#12481 ed7adc2 Thanks @dyc3! - Added the nursery rule noLateEventControl, which reports calls to preventDefault(), stopPropagation(), and stopImmediatePropagation() that run after the browser has finished handling the event, where they have no effect.
```
element.addEventListener("click", async (event) => {
  await save();
  event.preventDefault();
});
```
#12795 179666d Thanks @dyc3! - Added the nursery rule noMapSpread, which disallows spreading objects or arrays in the values returned by map() and flatMap() callbacks. Each spread copies a whole object or array for every item, which is slow for large arrays. Its unsafe fix replaces an object that starts with a spread with Object.assign().
```
const users = getUsers();
const rows = users.map((user) => ({ ...user, role: getRole(user) }));
```
#12793 d9a99fd Thanks @dyc3! - Added the nursery rule noMismatchedMapKey, which reports get() and set() calls that use a different key than the has() check before them. Checking one key and then using another is usually a copy-paste mistake.
```
if (map.has(key)) {
  map.get(otherKey); // reported
}
```
#12342 1db7c0d Thanks @vibbix! - Added the nursery rule noMissingScssInterpolation, which disallows Sass variables and function calls in custom property values without #{} interpolation. Sass copies these values into the CSS unchanged, so the browser receives $gap or math.div(8px, 2) instead of their results. Its unsafe fix wraps variables in #{}.
```
:root {
  --gap: $gap;
  --half: math.div(8px, 2);
}
```
#12792 de86b37 Thanks @dyc3! - Added the nursery rule noMissingThrow, which reports errors that are created with new but never thrown. Its unsafe fix adds the missing throw keyword.
```
function check(value) {
  if (!value) {
    new Error("Missing value");
  }
}
```
#12790 c23e4c3 Thanks @dyc3! - Added the new nursery rule noObjectLiteralComparison, which reports comparisons with an empty object {} or an empty array []. These comparisons never check whether a value is empty, because objects and arrays are compared by reference.
```
if (value === {}) {}
```
#12450 793f07d Thanks @dyc3! - Added the new nursery rule noPlaywrightUnsafeReferences, which reports functions passed to page.evaluate() or page.addInitScript() that use variables declared outside of them. Playwright runs these functions in the browser page, where those variables don't exist.
```
const x = 7;
await page.evaluate(() => x * 2); // reported: `x` must be passed as an argument
```
#12388 a0160a4 Thanks @vibbix! - Added the nursery rule noPseudoElementInFunctionalPseudoClass, which disallows pseudo-elements inside :is(), :where(), :not() and :has(). Browsers drop these selectors, so the styles never apply to the pseudo-element.
```
.card:is(::before, ::after) {
  content: "";
}
```
#12779 bc1befb Thanks @dyc3! - Added the new nursery rule noSinglePromiseInPromiseMethods, which reports an array with a single element passed to Promise.all(), Promise.any(), or Promise.race(). The rule offers a fix that awaits the value directly or uses Promise.resolve().
```
const result = await Promise.all([promise]);
```
#12241 d96de1d Thanks @dyc3! - Added the nursery rule noSvelteBindValueOnCheckableInputs, which reports bind:value on checkbox and radio inputs in Svelte files. Users change whether these inputs are checked, not their value, so bind:value does not track their choice.
```
<input type="checkbox" bind:value={accepted} />
```
#12764 e166d08 Thanks @dyc3! - Added the new nursery rule noSyncMethods, which reports calls to functions whose names end with Sync, such as fs.readFileSync(). These calls block the program until they finish. The allowAtRootLevel option allows them outside of functions, and the ignore option allows specific function names.
```
const contents = fs.readFileSync("data.txt");
```
#12515 c0a4174 Thanks @dyc3! - Added the nursery rule noTanstackQueryVoidQueryFn, which disallows TanStack Query functions that don't return any data. TanStack Query doesn't accept undefined as the data of a query, so the query fails with an error.
```
import { useQuery } from "@tanstack/react-query";

useQuery({
    queryKey: ["todos"],
    queryFn: async () => {
        await fetch("/api/todos");
    },
});
```
The rule belongs to the tanstackQuery and types domains.
#12482 1e6e407 Thanks @dyc3! - Added the nursery rule noUnnecessaryStringTrim, which reports trim() calls before startsWith() or endsWith() when only one side of the string matters. Use trimStart() or trimEnd() instead.
```
value.trim().startsWith("-");
```
#12772 a108773 Thanks @dyc3! - Added the nursery rule noUselessAwait, which reports await on values that are never promises, such as literals, arrays, and the results of comparisons.
```
await [fetchUser(), fetchPosts()];
```
#12783 d0931b0 Thanks @dyc3! - Added the new nursery rule noUselessLengthCheck, which reports array length checks that don't change the result: a check that the array is empty next to every(), a check that it isn't empty next to some(), or a check that it isn't empty around a for...of loop over the same array.
```
if (array.length > 0 && array.some(Boolean)) {}
```
#12488 93e0e73 Thanks @dyc3! - Added the new nursery rule noUselessTypeAssertion, which reports type assertions that don't change the type of an expression, such as a non-null assertion on a value that can't be null or undefined.
```
function double(value: number): number {
  return value! * 2;
}
```
#12632 0e197b4 Thanks @dyc3! - Added the nursery rule noVueChildContent, which disallows content inside elements that use v-html or v-text. These directives replace the content of their element, so Vue discards anything written there.
```
<template>
  <div v-html="html">Loading...</div>
</template>
```
#12616 cb7b888 Thanks @dyc3! - Added the new nursery rule noVueDeprecatedConfigKeyCodes, which reports uses of Vue.config.keyCodes. Vue 3 removed this option, so custom key names defined with it no longer work.
```
Vue.config.keyCodes = { f1: 112 };
```
#12568 59f3a42 Thanks @dyc3! - Added the nursery rule noVueDeprecatedDestroyedLifecycle, which reports the beforeDestroy and destroyed lifecycle hooks in Vue components. Vue 3 renamed them to beforeUnmount and unmounted, and no longer calls hooks with the old names.
```
<script>
export default {
  destroyed() {},
};
</script>
```
#12654 bcb1e0f Thanks @dyc3! - Added the nursery rule noVueDeprecatedEventsApi, which reports calls to the $on, $off, and $once instance methods in Vue components. Vue 3 removed these methods, so calling them throws an error.
```
<script>
export default {
  mounted() {
    this.$on("start", handler); // reported
  },
};
</script>
```
#12590 b9872ef Thanks @dyc3! - Added the nursery rule noVueDeprecatedFunctionalTemplate, which reports the functional attribute on the <template> of a Vue component. Vue 3 no longer supports this attribute.
```
<template functional>
  <div>{{ props.message }}</div>
</template>
```
#12552 b71b705 Thanks @dyc3! - Added the nursery rule noVueDeprecatedHtmlElementIs, which disallows the is attribute on HTML elements in Vue templates. Vue 3 no longer renders a component in place of these elements, unless the value starts with vue:.
```
<template>
  <tr is="my-row"></tr>
</template>
```
#12553 4a613e1 Thanks @dyc3! - Added the nursery rule noVueDeprecatedInlineTemplate, which disallows the inline-template attribute on Vue components. Vue 3 removed this feature, so the content between the component's tags is no longer used as its template.
```
<template>
  <my-component inline-template>
    <div>{{ message }}</div>
  </my-component>
</template>
```
#12617 0e9ca5b Thanks @dyc3! - Added the nursery rule noVueDeprecatedModelDefinition, which reports the model option in Vue components. Vue 3 ignores this option, so v-model on the component always uses the modelValue prop and the update:modelValue event.
```
<script>
export default {
  model: {
    prop: "checked",
    event: "change",
  },
};
</script>
```
#12604 e998921 Thanks @dyc3! - Added the nursery rule noVueDeprecatedPropsDefaultThis, which reports this inside the function that computes the default value of a Vue prop. Vue doesn't give this function access to the component, so this doesn't point to it. Read other props from the function's first argument instead.
```
<script>
export default {
  props: {
    size: Number,
    sizes: {
      type: Array,
      default() {
        return [this.size];
      },
    },
  },
};
</script>
```
#12633 f65fe1e Thanks @dyc3! - Added the nursery rule noVueDeprecatedSlotAttribute, which reports the slot attribute in Vue templates. Vue 3 no longer uses this attribute to fill named slots, so use v-slot (or #) on a <template> element instead.
```
<template>
  <MyComponent>
    <template slot="header">Title</template>
  </MyComponent>
</template>
```
#12589 8ccb19a Thanks @dyc3! - Added the new nursery rule noVueDeprecatedVBindSync, which reports the .sync modifier on Vue v-bind directives. Vue 3 removed this modifier, so the rule suggests v-model with the same argument instead.
```
<MyComponent :title.sync="pageTitle" />
```
#12609 e1e102b Thanks @dyc3! - Added the new nursery rule noVueDeprecatedVOnNativeModifier, which disallows the .native modifier on Vue's v-on directive. Vue 3 removed this modifier.
```
<MyComponent @click.native="onClick" />
```
#12667 de354e7 Thanks @dyc3! - Added the new nursery rule noVueExcessiveProps, which reports Vue components that declare more props than the maxProps option allows. The default limit is 10.
```

<script setup lang="ts">
defineProps<{ title: string; subtitle: string; icon: string }>(); // reported
</script>
```
#12666 c3dc557 Thanks @dyc3! - Added the nursery rule noVueLoneTemplate, which reports <template> elements inside a Vue template that don't use v-if, v-else-if, v-else, v-for, or v-slot. Vue renders these as regular HTML <template> elements, so their content isn't shown.
```
<template>
  <template>
    <p>Hello</p>
  </template>
</template>
```
#12533 4b1089d Thanks @dyc3! - Added the new nursery rule noVueMixin, which reports the mixins option in Vue components. In Vue 3, composables are the recommended way to share logic between components. The rule is recommended and part of the vue domain.
```
<script>
export default {
  mixins: [counterMixin],
};
</script>
```
#12658 807e358 Thanks @dyc3! - Added the new nursery rule noVueMultipleObjectsInClass, which reports :class arrays in Vue templates that contain more than one object. Merge the conditional classes into a single object instead.
```
<template>
  <div :class="[{ active: isActive }, { disabled: isDisabled }]" />
</template>
```
#12564 78c1dd5 Thanks @dyc3! - Added the nursery rule noVueRefObjectReactivityLoss, which reports reads of a Vue ref's value that run only once, in the same function that creates the ref. Such a read copies the current value, and the copy doesn't update when the ref changes.
```
import { ref } from "vue";

const count = ref(0);
const doubled = count.value * 2;
```
#12517 5044c56 Thanks @dyc3! - Added the nursery rule noVueRestrictedCallAfterAwait, which reports calls to configured functions that come after an await in a Vue component's setup() function.

For example, with { "functions": [{ "module": "vue-i18n", "path": "useI18n" }] }, the following call is reported:
```
<script>
import { useI18n } from "vue-i18n";

export default {
  async setup() {
    await fetchUser();
    const { t } = useI18n();
    return { t };
  },
};
</script>
```
#12558 e898da4 Thanks @dyc3! - Added the nursery rule noVueRestrictedVOn, which reports v-on event listeners that are disallowed through the listeners option. An entry can match an event name, a set of modifiers, and an element. For example, with { "listeners": [{ "event": "click", "element": "MyButton" }] }, <MyButton @click="onClick" /> is now reported.
#12573 65c6b0b Thanks [@dyc3](https:

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

coderabbitai · 2026-05-14T12:31:27Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: a341fad7-a6f0-4124-a668-cdb3febe0db1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

Trigger review

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Last reviewed commit: 6898c52
Latest commit, not reviewed: ee4881b

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

Bump CI action versions, pin pnpm to 11.1.2 in root and app, and update Changesets plus many app dependencies/devDependencies (Effect stack, TypeScript tooling, linting, testing, and build tools).

Changes

Toolchain and dependency upgrades

Layer / File(s)	Summary
GitHub Actions versions `.github/actions/setup/action.yml`, `.github/workflows/checking-dependencies.yml`, `.github/workflows/snapshot.yml`	pnpm action bumped to `@v6` in composite and workflow; `actions/setup-node` Node input updated to `24.15.0`; artifact upload action bumped to `actions/upload-artifact@v7`.
pnpm version pins `package.json`, `packages/app/package.json`	Workspace and app `packageManager` updated from `pnpm@10.30.1` to `pnpm@11.1.2`.
Dependency and toolchain upgrades `package.json`, `packages/app/package.json`	Root Changesets packages (`@changesets/changelog-github`, `@changesets/cli`) bumped; app package `dependencies` and `devDependencies` refreshed (Effect packages, ts-morph, Biome/ESLint, TypeScript tooling, Vitest/Vite, etc.).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

Dependency Dashboard effect-template#10: Overlaps pnpm/action-setup, pnpm pinning, and tooling/version updates.
Dependency Dashboard eslint-plugin-suggest-members#2: Matches workflow and pnpm/tooling bumps in CI and manifests.
Dependency Dashboard #1: Mirrors the same workflow and package.json version updates.
Dependency Dashboard dist-deps-prune#2: Contains similar dependency/version bump changes (pnpm, actions, packages).
Dependency Dashboard context-doc#5: Renovate-style workflow and package pin bumps align with that issue.
Dependency Dashboard effect-eslint-template#6: Shares pnpm and ESLint/Biome/tooling dependency updates.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description clearly documents the Renovate dependency, package manager, and GitHub Actions updates in the changeset.
Title check	✅ Passed	The title accurately identifies the pull request as a broad dependency update, including packages, tooling, and GitHub Actions.

Finishing Touches

Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch renovate/all

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

_{🐇 I nudged a YAML line, made pnpm climb to eleven,
Actions hum a newer tune, workflows light as heaven.
Packages refreshed, linters wake and play,
Tests tiptoe cleaner paths, building through the day.
✨}

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/actions/setup/action.yml:
- Line 13: The workflow currently uses a mutable tag "pnpm/action-setup@v6";
replace that with an immutable full commit SHA (40-hex) for pnpm/action-setup to
pin the action (e.g., "pnpm/action-setup@<full-commit-sha>"). Locate the "uses:
pnpm/action-setup@v6" entry in the action.yml and update it to the exact commit
SHA from the pnpm/action-setup repository, verify the SHA is full-length (40
characters) and that the workflow still runs correctly after the change.

In @.github/workflows/checking-dependencies.yml:
- Line 15: Replace the mutable tag reference "uses: pnpm/action-setup@v6" with
an immutable pin to the full commit SHA for the pnpm/action-setup action (e.g.,
"uses: pnpm/action-setup@<full-commit-sha>"); locate the occurrences of
"pnpm/action-setup@v6" in the workflow and update them to the corresponding
release commit SHA from the action's repository, then verify the workflow runs
successfully.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4cd2e52a-a23f-4849-8bc7-20b25e799703

📥 Commits

Reviewing files that changed from the base of the PR and between 6b3e168 and 373422e.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
package.json
packages/app/package.json

coderabbitai · 2026-05-14T12:34:25Z

  steps:
    - name: Install pnpm
-      uses: pnpm/action-setup@v3
+      uses: pnpm/action-setup@v6


⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash # Verify mutable action refs under .github (tag-based refs like `@v1/`@v6). # Expected: no matches after SHA pinning. rg -n --iglob '*.yml' --iglob '*.yaml' 'uses:\s*[^@[:space:]]+@v[0-9]+(\.[0-9]+){0,2}\b' .github

Repository: ProverCoderAI/openapi-effect

Length of output: 1009

Pin pnpm/action-setup to an immutable commit SHA.

Line 13 uses a mutable tag (@v6). Please pin to a full-length commit SHA to reduce supply-chain risk and avoid policy breaks in hardened org settings.

🔒 Suggested change

- uses: pnpm/action-setup@v6 + uses: pnpm/action-setup@<full-length-commit-sha> # v6.x

Reference: https://docs.github.com/actions/security-guides/security-hardening-for-github-actions

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/actions/setup/action.yml at line 13, The workflow currently uses a mutable tag "pnpm/action-setup@v6"; replace that with an immutable full commit SHA (40-hex) for pnpm/action-setup to pin the action (e.g., "pnpm/action-setup@<full-commit-sha>"). Locate the "uses: pnpm/action-setup@v6" entry in the action.yml and update it to the exact commit SHA from the pnpm/action-setup repository, verify the SHA is full-length (40 characters) and that the workflow still runs correctly after the change.

coderabbitai · 2026-05-14T12:34:25Z

    steps:
      - uses: actions/checkout@v6
-      - uses: pnpm/action-setup@v4
+      - uses: pnpm/action-setup@v6


⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash # Verify mutable action refs under .github (tag-based refs like `@v1/`@v6). # Expected: no matches after SHA pinning. rg -n --iglob '*.yml' --iglob '*.yaml' 'uses:\s*[^@[:space:]]+@v[0-9]+(\.[0-9]+){0,2}\b' .github

Repository: ProverCoderAI/openapi-effect

Length of output: 1009

Pin pnpm/action-setup to a commit SHA instead of a mutable tag.

Line 15 uses @v6, which is a mutable tag reference. Per GitHub's security hardening guidelines, action references should be pinned to full commit SHAs to ensure immutability and prevent unintended updates from tag rewrites.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/checking-dependencies.yml at line 15, Replace the mutable tag reference "uses: pnpm/action-setup@v6" with an immutable pin to the full commit SHA for the pnpm/action-setup action (e.g., "uses: pnpm/action-setup@<full-commit-sha>"); locate the occurrences of "pnpm/action-setup@v6" in the workflow and update them to the corresponding release commit SHA from the action's repository, then verify the workflow runs successfully.

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 6: The package.json currently sets "packageManager": "pnpm@11.1.2" but
pnpm v11 requires config and environment changes; run the recommended codemod
(pnpx codemod run pnpm-v10-to-v11) and then: move any settings under the
package.json "pnpm" field into pnpm-workspace.yaml, strip .npmrc to only
auth/registry entries, update .nvmrc and CI to Node.js 22+ to match pnpm v11,
rename any environment variables from npm_config_* to pnpm_config_ and manually
review remaining envs, and rename or invoke scripts named
clean/setup/deploy/rebuild using pnpm pm to avoid shadowing built-ins.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 78ded05a-1811-4eac-8349-84f29cb8618e

📥 Commits

Reviewing files that changed from the base of the PR and between 6898c52 and 57c74f4.

⛔ Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
package.json
packages/app/package.json

🚧 Files skipped from review as they are similar to previous changes (4)

.github/actions/setup/action.yml
.github/workflows/checking-dependencies.yml
.github/workflows/snapshot.yml
packages/app/package.json

coderabbitai · 2026-05-17T12:25:00Z

  "private": true,
  "description": "Monorepo workspace for effect-template",
-  "packageManager": "pnpm@10.30.1",
+  "packageManager": "pnpm@11.1.2",


⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

pnpm 11 breaking changes and migration guide

💡 Result:

pnpm 11 is a major release that introduces significant breaking changes, security-first defaults, and architectural improvements [1]. The official migration guide is available at https://pnpm.io/11.x/migration [2]. Key Breaking Changes and Migration Steps Configuration Changes pnpm 11 significantly changes how configuration is handled [3][1]: - Configuration is no longer read from the pnpm field in package.json; move these settings to pnpm-workspace.yaml [3][2]. -.npmrc files are now restricted to auth and registry settings only [3][1]. All other settings (e.g., hoist-pattern, node-linker) must be moved to pnpm-workspace.yaml using camelCase keys [3][2]. - npm_config_* environment variables are no longer supported; rename them to pnpm_config_* [3][1]. - pnpm no longer reads npm's global config at $PREFIX/etc/npmrc [1]. Dependency and Script Management - Build-dependency settings (onlyBuiltDependencies, neverBuiltDependencies, etc.) are consolidated into a single allowBuilds map in pnpm-workspace.yaml [3][1]. - Package manager strictness settings are collapsed into a single pmOnFail setting [3][2]. - Script names now shadow built-in commands [3]. If you have scripts named clean, setup, deploy, or rebuild, pnpm will execute your script instead of the built-in command; use pnpm pm to access the built-in version [3]. - pnpm install -g (with no arguments) is no longer supported; use pnpm add -g instead [3][1]. Environment and Infrastructure - Node.js 18, 19, 20, and 21 are no longer supported; Node.js 22+ is required [1]. - pnpm is now distributed as pure ESM [1]. - Global installs are now isolated using a global-virtual-store, preventing interference between global packages [1]. Security and New Features - Minimum Release Age: By default, pnpm 11 blocks the installation of package versions published within the last 24 hours to mitigate supply chain attacks [4][5][6]. - Exotic Subdependencies: pnpm 11 blocks dependencies resolved from non-standard sources (e.g., Git repositories or direct tarball URLs) by default [4][6]. - Native Publish: The npm CLI fallback for publishing has been removed in favor of a native implementation [1]. - Store Index: The store index has been migrated from a JSON-per-package format to a single SQLite database for improved performance [1][5]. Migration Tooling The pnpm team provides a codemod to automate many of these changes [2]. You can run it in your project directory: pnpx codemod run pnpm-v10-to-v11 [2] For changes that cannot be automated, such as environment variable updates, manual review is required [3][2].

Citations:

1: https://pnpm.io/blog/releases/11.0

2: https://pnpm.io/11.x/migration

3: https://pnpm.io/migration

4: https://gbhackers.com/pnpm-11-enables-default-release-age-guard/

5: https://cyberpress.org/pnpm-blocks-supply-attacks/

6: https://undercodenews.com/pnpm-11-reinvents-javascript-security-a-new-era-for-dependency-protection/

🌐 Web query:

pnpm 11.1.2 release notes and security advisories

💡 Result:

As of May 17, 2026, pnpm version 11.1.2 is the latest release [1]. Release Notes for pnpm 11.1.2 Specific release notes for version 11.1.2 were not explicitly detailed in the provided search results, as it is a very recent patch release [1]. However, it follows the major 11.1.0 and 11.1.1 releases, which introduced several significant features and fixes [2][3][4]: - New Commands: Added pnpm audit signatures (to verify ECDSA registry signatures), pnpm bugs (to open package bug trackers), and pnpm owner (to manage package owners) [3][4]. - Named Registries: Added support for installing packages from arbitrary named registries, including a built-in gh: prefix for the GitHub Packages npm registry [3][4]. - CI Improvements: Introduced the --no-runtime flag (config: runtime=false) to skip installing runtime entries (e.g., Node.js) in CI environments [3][4]. - Fixes: Version 11.1.1 included fixes for installability validation in workspace projects, resolved issues with pnpm add for named registries, and updated @zkochan/cmd-shim to improve compatibility with Git Bash on Windows [2]. Security Advisories There are no specific security advisories listed for version 11.1.2. Users should monitor the official pnpm GitHub Security Advisories page for any future disclosures [5]. Recent security-related updates in the pnpm 11 series include: - Minimum Release Age: pnpm 11 introduced a default Minimum Release Age of 24 hours (1440 minutes), which prevents the installation of newly published package versions to mitigate supply chain attacks [6][7][8]. - Enhanced Auditing: pnpm audit now queries the registry's bulk security advisories endpoint and filters by GitHub Advisory ID (GHSA) rather than CVE identifiers [9]. - Security Hardening: pnpm 11 requires Node.js 22+ and is distributed as pure ESM [10][11]. It also includes improved control over lifecycle scripts via the allowBuilds model [7][8]. For the most up-to-date information, always check the official pnpm releases page on GitHub and the security advisories section [12][5].

Citations:

1: https://www.npmjs.com/package/pnpm?activeTab=versions

2: https://github.com/pnpm/pnpm/releases/tag/v11.1.1

3: https://pnpm.io/blog/releases/11.1

4: https://newreleases.io/project/npm/pnpm/release/11.1.0

5: https://github.com/pnpm/pnpm/security/advisories

6: https://gbhackers.com/pnpm-11-enables-default-release-age-guard/

7: https://undercodenews.com/pnpm-11-reinvents-javascript-security-a-new-era-for-dependency-protection/

8: https://pnpm.io/supply-chain-security

9: https://pnpm.io/cli/audit

10: https://github.com/pnpm/pnpm/releases/tag/v11.0.0

11: https://pnpm.io/blog/releases/11.0

12: https://github.com/pnpm/pnpm/releases

Review pnpm 11 migration requirements before merging.

This major version upgrade introduces breaking changes that require configuration updates and environment adjustments:

Configuration files: Settings in package.json's pnpm field must move to pnpm-workspace.yaml. Update .npmrc to contain only auth and registry settings.

Node.js requirement: pnpm 11 requires Node.js 22+. Verify your project's .nvmrc and CI configuration specify a compatible version.

Environment variables: Any npm_config_* variables must be renamed to pnpm_config_*.

Script behavior: Scripts named clean, setup, deploy, or rebuild now shadow built-in commands; use pnpm pm to access built-in versions.

Run the migration codemod to automate configuration changes:

pnpx codemod run pnpm-v10-to-v11

Refer to https://pnpm.io/11.x/migration for the complete migration guide. Manual review is needed for environment variable updates that the codemod cannot automate.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@package.json` at line 6, The package.json currently sets "packageManager": "pnpm@11.1.2" but pnpm v11 requires config and environment changes; run the recommended codemod (pnpx codemod run pnpm-v10-to-v11) and then: move any settings under the package.json "pnpm" field into pnpm-workspace.yaml, strip .npmrc to only auth/registry entries, update .nvmrc and CI to Node.js 22+ to match pnpm v11, rename any environment variables from npm_config_* to pnpm_config_ and manually review remaining envs, and rename or invoke scripts named clean/setup/deploy/rebuild using pnpm pm to avoid shadowing built-ins.

skulidropek · 2026-06-19T19:15:56Z

Надо смержить сюда main ветку и исправить все ошибки в CI/CD что бы код был с актуальными библиотеками

konard · 2026-06-19T19:17:53Z

🤖 AI Work Session Started

Starting automated work session at 2026-06-19T19:17:51.406Z

The PR has been converted to draft mode while work is in progress.

This comment marks the beginning of an AI work session. Please wait for the session to finish, and provide your feedback.

konard · 2026-06-19T19:58:09Z

Update: the CI/CD fix is implemented and verified, but I cannot push it directly to this PR head branch.

Blocker:

PR fix(deps): update all dependencies #20 head is ProverCoderAI/openapi-effect:renovate/all.
Current GitHub credentials are konard and git push upstream renovate/all fails with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Prepared fix:

Commit: b16eac4b7948745fcd49d07e270b92f77b0ccb7d (fix(ci): adapt renovate update to pnpm 11)
Branch with the commit: konard/ProverCoderAI-openapi-effect:renovate/all

What the fix covers:

merged main into renovate/all locally;
moved pnpm 11 config from package.json#pnpm into pnpm-workspace.yaml and kept release-age policy with exact excludes;
pinned pnpm/action-setup to full SHA 0ebf47130e4866e96fce0953f49152a61190b271 (v6.0.9);
updated CI Node runtime to 24.17.0 so pnpm 11 can load node:sqlite;
fixed TypeScript 6/lint fallout while preserving legacy public aliases;
added consumer compile proof for the legacy serializer aliases.

Verification:

Local: pnpm install --frozen-lockfile && pnpm check && pnpm build && pnpm lint:effect && pnpm test && pnpm --filter @prover-coder-ai/openapi-effect test:consumer && pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent passed with Node 24.17.0 / pnpm 11.8.0.
Fork CI Check passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27845776274
Fork CI Checking Dependencies passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27845776279

Needed human action: either grant/push access to ProverCoderAI/openapi-effect:renovate/all, or cherry-pick b16eac4b7948745fcd49d07e270b92f77b0ccb7d from the fork branch into the PR head branch.

konard · 2026-06-19T19:59:20Z

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $21.304392

📊 Context and tokens usage:

508.9K / 200K (254%) input tokens, 68.4K / 128K (53%) output tokens

Total: (508.9K + 13.1M cached) input tokens, 68.4K output tokens, $21.304392 cost

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Thinking level: max (~31999 tokens)
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (75696KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:01:31Z

🔄 Auto-restart triggered (iteration 1)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:09:42Z

Rechecked the failing CI/CD status in this restart session.

Findings:

Latest upstream PR runs are still for old SHA 48c4a8472fb0d70d3d48c14f5963a2d421a90ec7 from 2026-06-19T13:11:52Z.
Logs saved locally during investigation show the failures are from pnpm 11 running on Node 20.16.0 / 22.12.0 and from pnpm 11 ignoring package.json#pnpm, causing minimumReleaseAge violations.
The prepared fix commit is still b16eac4b7948745fcd49d07e270b92f77b0ccb7d on konard/ProverCoderAI-openapi-effect:renovate/all.

Verification repeated locally with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint:effect
pnpm lint
pnpm test
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback artifact check via npm pack

Fork CI also has successful runs for b16eac4: Check 27845776274, Checking Dependencies 27845776279.

Remaining blocker is repository permissions, not code: git push upstream renovate/all still fails with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard. Please either grant push access to ProverCoderAI/openapi-effect:renovate/all or cherry-pick/push b16eac4b7948745fcd49d07e270b92f77b0ccb7d from the fork branch into the upstream PR head branch.

konard · 2026-06-19T20:11:08Z

🔄 Auto-restart-until-mergeable Log (iteration 1)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.197492
Token usage: 93,621 input, 17,194 output, 5,819 reasoning, 2,487,552 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (96784KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:13:21Z

🔄 Auto-restart triggered (iteration 2)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:22:22Z

Rechecked and updated the prepared fix in this restart session.

Current prepared commit:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
This includes the earlier CI/pnpm 11 fix plus a small follow-up commit fix(app): satisfy strict type lint example so lint:types also passes.

Root causes confirmed from upstream CI logs for old SHA 48c4a8472fb0d70d3d48c14f5963a2d421a90ec7:

Check/Snapshot: pnpm 11 ran under an old Node runtime and failed on node:sqlite / Node >= 22.13 requirement.
dist-deps-prune: pnpm 11 minimum release age policy rejected fresh lockfile entries.

Verification on current SHA b52bed1:

Local with Node 24.17.0 and pnpm 11.8.0: pnpm install --frozen-lockfile, pnpm check, pnpm build, pnpm lint, pnpm lint:effect, pnpm test, pnpm lint:tests, pnpm --filter @prover-coder-ai/openapi-effect lint:types, pnpm --filter @prover-coder-ai/openapi-effect test:consumer, pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent, and package pack check all passed.
Fork CI Check passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721442
Fork CI Checking Dependencies passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721454
Fork Snapshot is skipped by the workflow owner guard (github.repository_owner == 'ProverCoderAI'); the equivalent local pnpm build plus fallback npm pack artifact path passed.

Remaining blocker is repository permission, not code. git push upstream renovate/all still fails with:

remote: Permission to ProverCoderAI/openapi-effect.git denied to konard.
fatal: unable to access 'https://github.com/ProverCoderAI/openapi-effect.git/': The requested URL returned error: 403

Needed maintainer action: push/cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from the fork branch into ProverCoderAI/openapi-effect:renovate/all. Until that happens, PR #20 remains on the old upstream head SHA 48c4a8472fb0d70d3d48c14f5963a2d421a90ec7 and will keep showing stale failing checks.

konard · 2026-06-19T20:24:34Z

🔄 Auto-restart-until-mergeable Log (iteration 2)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.788024
Token usage: 95,677 input, 18,030 output, 5,431 reasoning, 3,019,904 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (116514KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:26:47Z

🔄 Auto-restart triggered (iteration 3)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:33:49Z

Restart iteration 3 rechecked the prepared CI fix.

Current verified head:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
Local branch includes upstream/main via merge commit f43684a.
PR fix(deps): update all dependencies #20 still points to ProverCoderAI/openapi-effect:renovate/all@48c4a8472fb0d70d3d48c14f5963a2d421a90ec7, so its failing checks are stale for the old head.

Fresh upstream CI logs downloaded in this session confirm old-head root causes:

Check: pnpm 11 under Node 20.16.0 fails on node:sqlite / Node >= 22.13 requirement.
Snapshot: pnpm 11 under Node 22.12.0 fails the Node >= 22.13 requirement.
Checking Dependencies: pnpm 11 ignores package.json#pnpm and then fails minimumReleaseAge for the refreshed lockfile entries.

Verification repeated on b52bed1 with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint
pnpm lint:effect
pnpm test
pnpm lint:tests
pnpm --filter @prover-coder-ai/openapi-effect lint:types
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback npm pack artifact path

Push blocker remains external:
git push upstream HEAD:renovate/all fails with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Needed maintainer action: push or cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from the fork branch into ProverCoderAI/openapi-effect:renovate/all.

konard · 2026-06-19T20:35:31Z

🔄 Auto-restart-until-mergeable Log (iteration 3)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.433867
Token usage: 92,361 input, 16,725 output, 5,362 reasoning, 2,757,632 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (139990KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:37:44Z

🔄 Auto-restart triggered (iteration 4)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:44:12Z

Restart iteration 4 rechecked the CI/CD fix.

Current verified head:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
upstream/main is merged into this branch.
PR fix(deps): update all dependencies #20 upstream head is still ProverCoderAI/openapi-effect:renovate/all@48c4a8472fb0d70d3d48c14f5963a2d421a90ec7, so the visible failing checks are still for the old head.

Fresh upstream logs downloaded in this session confirm the old-head failures:

Check: pnpm 11 runs under Node 20.16.0 and fails on node:sqlite / Node >= 22.13.
Snapshot: pnpm 11 runs under Node 22.12.0 and fails the Node >= 22.13 requirement.
Checking Dependencies: pnpm 11 rejects fresh lockfile entries through minimumReleaseAge.

Verification repeated locally on b52bed1 with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint
pnpm lint:effect
pnpm test
pnpm lint:tests
pnpm --filter @prover-coder-ai/openapi-effect lint:types
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback artifact check via npm pack

Push status:

git push origin HEAD:renovate/all: up to date.
git push upstream HEAD:renovate/all: blocked with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Needed maintainer action: push or cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from konard/ProverCoderAI-openapi-effect:renovate/all into ProverCoderAI/openapi-effect:renovate/all. Until then PR #20 cannot receive fresh CI for the verified fix.

konard · 2026-06-19T20:45:53Z

🔄 Auto-restart-until-mergeable Log (iteration 4)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.654120
Token usage: 127,152 input, 17,640 output, 5,582 reasoning, 2,588,800 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (154923KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:48:07Z

🔄 Auto-restart triggered (iteration 5)

Reason: CI failures detected

Starting new session to address the issues.

Auto-restart-until-mergeable mode is active. This run will stop after 5 restart iterations.

konard · 2026-06-19T20:54:43Z

Restart iteration 5 rechecked the CI/CD failures and the prepared fix.

Current verified fix:

b52bed11666e71930f1d563062826936f36fd5f3 on konard/ProverCoderAI-openapi-effect:renovate/all
This branch includes upstream/main and has origin/renovate/all up to date.

Fresh upstream CI status:

PR fix(deps): update all dependencies #20 still points to ProverCoderAI/openapi-effect:renovate/all@48c4a8472fb0d70d3d48c14f5963a2d421a90ec7.
Latest upstream runs are still from 2026-06-19T13:11:52Z for that old SHA:
- Check 27827776411: failure
- Checking Dependencies 27827776440: failure
- Snapshot 27827776423: failure

Root causes confirmed from downloaded upstream logs:

Check jobs (Build, Types, Lint, Lint Effect-TS, Test) fail before project code because pnpm 11 runs under Node 20.16.0 and errors with No such built-in module: node:sqlite / Node >= 22.13 requirement.
Snapshot fails for the same pnpm 11 runtime requirement under Node 22.12.0.
dist-deps-prune fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION for effect@3.21.4, eslint-plugin-sonarjs@4.1.0, and eslint-plugin-unicorn@68.0.0.

Verification repeated locally on b52bed1 with Node 24.17.0 and pnpm 11.8.0:

pnpm install --frozen-lockfile
pnpm check
pnpm build
pnpm lint
pnpm lint:effect
pnpm test
pnpm lint:tests
pnpm --filter @prover-coder-ai/openapi-effect lint:types
pnpm --filter @prover-coder-ai/openapi-effect test:consumer
pnpm dlx @prover-coder-ai/dist-deps-prune scan --package ./packages/app/package.json --prune-dev true --silent
snapshot fallback artifact path via npm pack

Fork CI on b52bed1:

Check passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721442
Checking Dependencies passed: https://github.com/konard/ProverCoderAI-openapi-effect/actions/runs/27846721454
Snapshot skipped by the workflow owner guard (github.repository_owner == 'ProverCoderAI'); the equivalent local build plus fallback pack path passed.

Push status:

git push origin HEAD:renovate/all: up to date.
git push upstream HEAD:renovate/all: blocked with 403 Permission to ProverCoderAI/openapi-effect.git denied to konard.

Needed maintainer action: push or cherry-pick b52bed11666e71930f1d563062826936f36fd5f3 from konard/ProverCoderAI-openapi-effect:renovate/all into ProverCoderAI/openapi-effect:renovate/all. Until that upstream PR head moves off 48c4a84, the visible PR checks remain stale failures for the old commit.

konard · 2026-06-19T20:56:07Z

🔄 Auto-restart-until-mergeable Log (iteration 5)

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

Model: GPT-5.5
Provider: OpenAI
Public pricing estimate: $4.888533
Token usage: 166,658 input, 16,101 output, 4,054 reasoning, 2,497,408 cache read

🤖 Models used:

Tool: OpenAI Codex
Requested: gpt-5.5
Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (177139KB)

View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

konard · 2026-06-19T20:58:19Z

⚠️ Auto-restart limit reached

Hive Mind stopped auto-restart-until-mergeable after 5 restart iterations.

Configured limit: 5
Remaining reason: CI failures detected

No further AI sessions will be started automatically for this run. Please review the remaining blockers manually or rerun with a higher --auto-restart-max-iterations value.

Auto-restart-until-mergeable stopped by the safety limit.

konard · 2026-06-19T20:58:26Z

🤖 AI Work Session Completed

Work session ended at 2026-06-19T20:58:19.771Z

The PR will be converted back to ready for review.

This comment marks the end of an AI work session. New comments after this time will be considered as feedback.

renovate Bot assigned skulidropek Feb 21, 2026

renovate Bot requested a review from skulidropek February 21, 2026 13:44

renovate Bot force-pushed the renovate/all branch from 61f06bc to 4c58bf8 Compare February 23, 2026 22:47

renovate Bot changed the title ~~fix(deps): update dependency effect to ^3.19.19~~ fix(deps): update all dependencies Feb 23, 2026

renovate Bot force-pushed the renovate/all branch 9 times, most recently from 52aba09 to 16d549f Compare March 2, 2026 17:40

renovate Bot force-pushed the renovate/all branch 10 times, most recently from f240877 to 3c2e51f Compare March 9, 2026 23:06

renovate Bot force-pushed the renovate/all branch 7 times, most recently from 9456c54 to 0ff8d9f Compare March 17, 2026 14:38

renovate Bot force-pushed the renovate/all branch 5 times, most recently from 6ff8486 to 4c77644 Compare April 24, 2026 02:39

coderabbitai Bot requested changes May 14, 2026

View reviewed changes

coderabbitai Bot requested changes May 17, 2026

View reviewed changes

fix(deps): update all dependencies

ee4881b

Conversation

renovate Bot commented Feb 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.6.6

Patch Changes

v2.6.5

Patch Changes

Configuration

Uh oh!

coderabbitai Bot commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Reviews paused

Changes

Estimated code review effort

Possibly related issues

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 14, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 17, 2026

Choose a reason for hiding this comment

Uh oh!

skulidropek commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

🤖 Solution Draft Log

💰 Cost estimation:

📊 Context and tokens usage:

🤖 Models used:

📎 Log file uploaded as Repository (75696KB)

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart triggered (iteration 1)

Uh oh!

konard commented Jun 19, 2026

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart-until-mergeable Log (iteration 1)

💰 Cost estimation:

🤖 Models used:

📎 Log file uploaded as Repository (96784KB)

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart triggered (iteration 2)

Uh oh!

konard commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart-until-mergeable Log (iteration 2)

💰 Cost estimation:

🤖 Models used:

📎 Log file uploaded as Repository (2 chunks) (116514KB)

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart triggered (iteration 3)

Uh oh!

konard commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

konard commented Jun 19, 2026

🔄 Auto-restart-until-mergeable Log (iteration 3)

💰 Cost estimation:

🤖 Models used:

📎 Log file uploaded as Repository (2 chunks) (139990KB)

renovate Bot commented Feb 21, 2026 •

edited

Loading

`v2.6.6`

`v2.6.5`

coderabbitai Bot commented May 14, 2026 •

edited

Loading

konard commented Jun 19, 2026 •

edited

Loading

konard commented Jun 19, 2026 •

edited

Loading