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.5.12`	devDependencies	minor
@changesets/changelog-github (source)	`^0.5.2` → `^1.0.1`	devDependencies	major
@changesets/cli (source)	`^2.29.8` → `^3.0.2`	devDependencies	major
@eslint-community/eslint-plugin-eslint-comments	`^4.6.0` → `^4.7.2`	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` → `^24.13.3`	devDependencies	minor
@typescript-eslint/eslint-plugin (source)	`^8.56.0` → `^8.69.0`	devDependencies	minor
@typescript-eslint/parser (source)	`^8.56.0` → `^8.69.0`	devDependencies	minor
@vitest/coverage-v8 (source)	`^4.0.18` → `^5.0.0`	devDependencies	major
@vitest/eslint-plugin	`^1.6.9` → `^1.6.27`	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` → `^3.22.1`	dependencies	minor
eslint (source)	`^10.0.1` → `^10.10.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.0`	devDependencies	minor
eslint-plugin-unicorn	`^63.0.0` → `^74.0.0`	devDependencies	major
globals	`^17.3.0` → `^17.12.0`	devDependencies	minor
jscpd (source)	`^4.0.8` → `^5.1.2`	devDependencies	major
node	`24.13.1` → `24.20.0`	uses-with	minor
pnpm (source)	`10.30.1` → `11.25.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.69.0`	devDependencies	minor
vite (source)	`^7.3.1` → `^8.2.2`	devDependencies	major
vitest (source)	`^4.0.18` → `^5.0.0`	devDependencies	major

cc @skulidropek

Release Notes

biomejs/biome (@biomejs/biome)

`v2.5.12`

Compare Source

Patch Changes

#11440 b88f1ea Thanks @Princesseuh! - Fixed Astro attribute expressions rejecting TypeScript and JSX syntax that is accepted in text expressions.
```
<Component icon={<Icon />} count={total as number} onSelect={(e: Event) => e} />
```
#11440 b88f1ea Thanks @Princesseuh! - Fixed Astro attribute names being split on : and . inside an expression, such as {x && <button x-on:keyup.enter={go} client:load.foo />}.
#11440 b88f1ea Thanks @Princesseuh! - Fixed a bare > in the children of an Astro expression being treated as markup, such as {x && <div>a > b</div>}.
#11440 b88f1ea Thanks @Princesseuh! - Fixed HTML comments inside an Astro expression failing to parse. They are now read as trivia, wherever they appear among the children.
```
{x && <div>text</div>}
{cond && <a></a><b></b>}
```
#11440 b88f1ea Thanks @Princesseuh! - Fixed is:raw children inside an Astro expression being read as JSX, such as {x && <div is:raw>{not js} < & text</div>}.
#11440 b88f1ea Thanks @Princesseuh! - Fixed an apostrophe or quote in the text of a JSX element inside an Astro expression ending the expression early, such as {items.map((i) => <li>it's {i}</li>)}.
#11440 b88f1ea Thanks @Princesseuh! - Fixed the children of a <script> or <style> inside an Astro expression being read as JSX. Their contents are text, so braces and comparisons no longer have to be escaped.
```
{cond && <style>a { color: red }</style>}
{cond && <script>let x = {a: 1};</script>}
```
#11440 b88f1ea Thanks @Princesseuh! - Added support for template literal attribute values inside an Astro expression, such as {x && <C data-x=`t${x}` />}.
#11440 b88f1ea Thanks @Princesseuh! - Fixed unquoted attribute values being rejected inside an Astro expression, such as {x && <a class=foo maxlength=255 href=/about>go</a>}.
#11440 b88f1ea Thanks @Princesseuh! - Fixed a template literal nested inside ${} breaking the rest of an Astro file, such as const href = `/blog${page === 0 ? '' : `/${page + 1}`}`;.
#11440 b88f1ea Thanks @Princesseuh! - Fixed a quote inside a regex character class breaking the rest of an Astro file, such as const unsafe = /[/"]/;.
#11508 54f3a2e Thanks @dyc3! - Added the nursery rule useFlatMathMinMax. Because Math.min() and Math.max() accept any number of arguments, the rule reports unnecessary nested calls to the same method:
```
Math.max(Math.max(a, b), c);
```
The fix flattens this expression to Math.max(a, b, c).
#11585 c5c8315 Thanks @Netail! - Fixed #11475: noUnresolvedImports no longer reports Bun runtime built-in modules (bun, bun:bundle, bun:ffi, bun:jsc, bun:sqlite, bun:test).
#11368 52a57b3 Thanks @Austin1serb! - Fixed #6830: Biome now reports a diagnostic for excessively deep syntax instead of overflowing the native stack while releasing the parsed tree.
#11596 1fc42ed Thanks @dyc3! - Added the nursery rule noThisOutsideOfClass. The rule reports this outside class members and TypeScript functions with an explicit this parameter.
```
function Person(name) {
    this.name = name;
}
```
#11555 2516335 Thanks @dyc3! - Fixed #11529, where noFloatingPromises missed unhandled Promise chains when the imported function's module belonged to an import cycle. Cyclic modules now preserve types for exports that do not participate in recursive type dependencies.
#11518 0fee70c Thanks @HarperZ9! - Fixed #11500: the formatter now prints the declare modifier before accessibility modifiers on class properties. private declare readonly name: string is now formatted as declare private readonly name: string, matching Prettier and TypeScript's canonical modifier order.
#11580 1277af2 Thanks @ematipico! - Fixed #5091: Biome no longer moves comments next to the < of a generic, which causes invalid TypeScript syntax:
```
- Generic<// a comment
+ Generic<
+   // a comment
```
#11577 42995d2 Thanks @ematipico! - Fixed #4592. Biome no longer crashes while parsing malformed delete expressions.
#11590 67963b4 Thanks @ematipico! - Fixed #6427 so Grit plugins can use function = ... as a node argument.
#11600 a689cb5 Thanks @ematipico! - Fixed #6644: noUnusedVariables now recognizes all interface declarations in a TypeScript declaration-merging group when the interface is referenced.

The following snippet no longer triggers the rule.
```
interface Things {
    foo: string;
}

interface Things {
    bar: string;
}

export type Key = keyof Things;

interface Things {
    baz: string;
}
```
#11591 d4a0716 Thanks @ematipico! - Fixed #6615. noDuplicateProperties no longer reports declarations nested in block at-rules as duplicates of declarations in their parent block.
#11492 f2a07aa Thanks @santichausis! - Fixed #11454: noMisplacedAssertion now recognises @fast-check/vitest's test.prop(...) (and .concurrent.prop, .skip.prop, etc.) as a test function, the same way it already recognises test.each. The JS formatter picks up the same recognition, so a curried test.prop(...)(...) call is now formatted with the regular breakable argument layout used for test.each/test.for, instead of the single-line-hugging layout used for plain it/test calls.

For example, Biome no longer reports the assertion below as misplaced:
```
import { fc, test } from "@fast-check/vitest";

test.prop([fc.string()])("round-trips", (s) => {
  expect(s).toBe(s);
});
```
#11589 65742b3 Thanks @ematipico! - Fixed #4928: noUnusedVariables no longer reports a value declaration as unused when its merged namespace is referenced.
#11559 472dbc2 Thanks @levrik! - Fixed a false positive in noVueDuplicateKeys where a <script setup> variable initialized from props was reported as a duplicate of the prop it derives from. Biome now exempts any variable whose initializer references props, instead of only recognizing defineProps() and toRefs(props).

For example, Biome no longer reports foo below as a duplicate key:
```
<script setup>
import { toRef } from 'vue';
const props = defineProps(['foo']);
const foo = toRef(props, 'foo');
</script>
```
#11594 6586ceb Thanks @ematipico! - Fixed #6640. Biome no longer crashes when linting malformed for...of statements.
#11571 85b197d Thanks @ematipico! - Fixed #10838: useSortedAttributes no longer corrupts JSX attributes when nested JSX elements also require sorting.
#11533 97e76c0 Thanks @ematipico! - Fixed #11520, where the Biome scanner would start analysing dependencies multiple times, leading to long and unresponsive sessions.
#11564 18a0e1f Thanks @Netail! - Fixed the diagnostic range of noInferrableTypes so it now highlights only the type instead of including the leading : colon, spaces and comments.
#11540 124fdaa Thanks @ematipico! - Fixed #11537: noShorthandPropertyOverrides now compares declarations only within the same block. The rule no longer reports @supports feature queries and correctly checks nested, @keyframes, and @page blocks.
#11532 7ceb0ee Thanks @dyc3! - Fixed #11528: noFloatingPromises no longer reports statement-level await expressions that handle Promise values, including overloaded calls returning Promise aliases. Awaited values that resolve to arrays of Promises remain reported because their element Promises are not handled by await.
#11474 3c6412e Thanks @dyc3! - Fixed #10241. Biome no longer reports unsupported text expression diagnostics for double-curly text in vanilla HTML, and the formatter preserves adjacent curly-brace text.
#11593 6c7fd27 Thanks @dyc3! - Added the nursery rule noVueDeprecatedScopedSlots. It reports deprecated $scopedSlots references in Vue templates and component objects, and offers an unsafe replacement with $slots. For example, Biome now reports this.$scopedSlots.default inside a Vue component.
#11440 b88f1ea Thanks @Princesseuh! - Fixed the formatter crashing on an Astro or Svelte expression spanning several lines in a file with CRLF line endings, such as <p>{a +\r\n b}</p>.
#11581 f4e5ebb Thanks @dyc3! - Added the nursery rule useModernMathApis. The rule reports legacy mathematical patterns that have direct modern Math equivalents.
```
Math.sqrt(a * a + b * b);
```
#11597 a20f44a Thanks @Netail! - Added the nursery rule noBunModules, which forbids the use of Bun builtin modules (e.g. bun:sqlite, bun:ffi).
#11545 7d54688 Thanks @dyc3! - Fixed #11542: Biome now reports HTML comments between Svelte tag attributes as parse errors.
#11582 b6611dd Thanks @ematipico! - Fixed #3862. Biome now parses legacy Internet Explorer filter and -ms-filter values such as progid:DXImageTransform... and alpha(opacity=40).
#11575 65da251 Thanks @dyc3! - Improved the Tailwind parser's ability to recover from parsing failures. Whitespace now always allows the parser to recover and start parsing a new class.
#11576 0f78499 Thanks @ematipico! - Fixed #3515 and #10395, where Biome could corrupt Unicode characters while writing source received through standard input to standard output. Characters such as ⚠ and ✔ are now preserved.
#11539 0fca643 Thanks @ematipico! - Fixed #11512, where style/noDescendingSpecificity missed lower-specificity selectors after a later higher-specificity selector with the same tail selector.
#11544 040f867 Thanks @dyc3! - Fixed #11541: formatting a Svelte render tag followed by an HTML comment no longer duplicates the comment.
```
 <div>
   {@render children?.()}
   
-  
 </div>
```
#11565 ee69e0e Thanks @ematipico! - Fixed #11525. Now the configuration schema correctly provides auto-completion for linter domains.
#11583 b19390c Thanks @dyc3! - Fixed #11352: useExplicitLengthCheck no longer reports length-like properties used as value-producing || fallbacks or optional chains, and it no longer offers fixes for value-producing && checks or unsafe negations.
#11562 753e955 Thanks @ematipico! - Fixed an issue where the Biome Language Server would start with logging level set to debug. This would cause logs to grow exponentially in long sessions.
#11217 7d3ee9c Thanks @dyc3! - Fixed handling of biome-ignore format suppression comments on TypeScript declared class properties with string literal names.
```
class A {
	declare /* biome-ignore format: exercise suppression checking */ 'a-b': 0;
}
```
#11497 f5d7896 Thanks @dyc3! - Added the noInvalidFileInputAccept nursery rule. The rule reports invalid literal accept values on file inputs in JSX and HTML, and normalizes common mistakes.
```
<input type="file" accept="image/jpg" />
```
#11345 ac58958 Thanks @jakeleventhal! - Improved type inference performance by avoiding resolution of unused members in object arguments.
#11554 2d55931 Thanks @Netail! - Added the new nursery rule useReactNamingConvention, which enforces naming conventions for React values assigned from createContext, useId, and useRef. A value from createContext must be a PascalCase component name ending with Context, a value from useId must be named id or end with Id, and a value from useRef must be named ref or end with Ref.
#11491 1d6210b Thanks @dyc3! - Added the nursery rule noUnmodifiedLoopCondition, which reports variables in loop conditions that are never modified in the loop.
```
let node = getNode();
while (node) {
    process(node);
}
```

`v2.5.11`

Compare Source

Patch Changes

#11499 9743d0c Thanks @scs0209! - Fixed #11496: useValidAnchor now treats Astro JSX shorthand attributes like <a {href}> as a valid href.
#11437 88f805e Thanks @Princesseuh! - Fixed #9944: adjacent elements inside an Astro expression now parse as an implicit fragment instead of raising an error.
```
{options.map(() =>
  <div />
  <div />
)}
```
#11437 88f805e Thanks @Princesseuh! - Fixed Astro templates rejecting unclosed HTML void elements, such as {cond && <br>}.
#11507 e2fc036 Thanks @dyc3! - Fixed #11157: noUnusedVariables no longer reports Vue <script setup> bindings used by CSS v-bind() as unused.
#11398 afc4615 Thanks @dyc3! - Fixed #11389: Files passed through --stdin-file-path now use full HTML support for Astro, Svelte, and Vue when it is enabled.
#11526 372cd68 Thanks @dyc3! - Fixed noVueRefAsOperand to track Vue refs through declaration aliases and toRefs() properties, and to recognize useTemplateRef() results. The rule no longer reports false positives such as plain ref transfers, plain toRefs() property access, defineModel() modifiers, or the supported .effect member as operands.

The refactor enabling these fixes also improves the performance of the rule.
#11458 a7cd286 Thanks @dyc3! - Fixed #11436: GritQL snippets such as export { $specifiers } from $source now match named re-exports with aliases, inline type modifiers, and multiple specifiers.
#11515 382b15d Thanks @dyc3! - Fixed #11390, where noFloatingPromises performed expensive full type inference for calls to non-Promise methods declared on third-party TypeScript classes. The rule now classifies those calls using targeted type information.
#11516 6f40e82 Thanks @levrik! - Fixed noVueRefAsOperand so it no longer reports a callback parameter (e.g. from .find(), .map()) as an unwrapped ref value just because it's nested inside a ref(), computed(), or similar call.
```
const result = computed(() => list.find((item) => item.label === "a"));
```
Previously, item here was incorrectly treated as a ref value because the rule attributed it to the outer computed() call.
#11495 496268d Thanks @Netail! - Fixed useGraphqlNamingConvention so it no longer reports GraphQL enum value definitions with comments & descriptions and now displays a more accurate diagnostic range.
#11407 6ef52b0 Thanks @1678092075! - Fixed #11214: noUnusedVariables no longer reports type parameters declared by non-default function overload signatures that have an implementation.
#11322 5c353e6 Thanks @jp-knj! - Added a new nursery rule noAstroSetHtmlDirective, which disallows Astro's set:html directive because untrusted content can introduce cross-site scripting vulnerabilities.

For example, the following snippet triggers the rule:
```
<div set:html={content} />
```
#11462 18883b7 Thanks @dyc3! - Fixed #10776: useVueHyphenatedAttributes no longer reports lowercase attribute names containing punctuation, such as pt:header:data-test-id and some_attr.
#11476 3270ca4 Thanks @dyc3! - Fixed #10330: Vue interpolation delimiters now stay attached to whitespace-sensitive element boundaries and adjacent inline siblings, wrapping their expression when needed to fit the configured line width. Interpolations followed by text now also converge after one formatting pass.
```
-<v-btn v-if="store.state.user" variant="text" to="/my-rooms"
-  >{{ $t("nav.my-rooms") }}</v-btn
->
+<v-btn v-if="store.state.user" variant="text" to="/my-rooms">{{
+  $t("nav.my-rooms")
+}}</v-btn>
```
#11191 3e5367f Thanks @ematipico! - Added the nursery rule noUndeclaredCustomProperties, which reports references to custom properties that are not defined in available CSS, static HTML-like style attributes, or JSX string style attributes.

For example, the following snippet triggers the rule:
```
a { color: var(--undefined-color); }
```

#11435 7754894 Thanks @levrik! - Fixed: Variables and imports used as custom Vue directives are no longer reported as unused.

For example:

<script setup>
const vHighlight = {
  mounted: (element) => {
    element.style.color = "red";
  },
};
</script>

<template>
  <p v-highlight>Hello</p>
</template>

#11501 e6acded Thanks @aminya! - Improved the performance of useArraySortCompare by skipping type inference for calls to unrelated methods.
#11467 66b282c Thanks @dyc3! - Fixed #11464: Biome now parses parenthesized object literals returned from arrow functions when they contain a conditional expression and a nested arrow function.
#11456 db9aa2a Thanks @dyc3! - Fixed #10278: Marked the fix for noThisInStatic as unsafe by default.
#11502 652aedb Thanks @levrik! - noGlobalAssign no longer reports assignments to a Vue <script setup> binding from a template expression, when the binding's name happens to match a built-in global (e.g. open, parent, top).

For example, this no longer triggers a diagnostic:
```
<script setup>
const open = defineModel();
</script>

<template>
  <button @click="open = !open">Toggle</button>
</template>
```

`v2.5.10`

Compare Source

Patch Changes

#11403 8f7786f Thanks @Princesseuh! - Fixed Astro rejecting JavaScript comments between attributes.
```
<div /* block comment */ class="something"></div>
<Component /* c */ client:load />
```
#11403 8f7786f Thanks @Princesseuh! - Fixed a bare < in Astro text being treated as the start of a tag, such as <p>5 < 6 and 7 > 6</p>. As in HTML, a < that cannot open a tag is text and needs no escaping.
#11438 3133ffa Thanks @Princesseuh! - Fixed #8294: an Astro expression holding only a comment is no longer reported as a parse error, which also stopped the whole file from being formatted.
```
<div>{/* a note */}</div>
<div class={/* a note */}>x</div>
```
#11403 8f7786f Thanks @Princesseuh! - Fixed #9165: an empty Astro expression such as <div>{}</div> no longer fails to parse. Astro renders {} as nothing.
#11403 8f7786f Thanks @Princesseuh! - Fixed Astro expressions containing a comment failing to parse.
```
<div>{/* block comment */ x}</div>
<div>{/* only a comment */}</div>
```
#11403 8f7786f Thanks @Princesseuh! - Added support for Astro's fragment shorthand.
```
<>
  <p>a</p>
</>
```
#11403 8f7786f Thanks @Princesseuh! - Fixed an Astro frontmatter block being cut short by a closing tag inside a string or comment.
```
---
const a = "</script>";
// </script> in a comment
---
```
#11403 8f7786f Thanks @Princesseuh! - Fixed --- being read as an Astro frontmatter fence when markup precedes it. Astro only recognizes frontmatter at the very start of a file, so a file opening with a comment now has no frontmatter, and its --- lines are content.
```

---
this is text, not frontmatter
---
```
#11403 8f7786f Thanks @Princesseuh! - Fixed an Astro frontmatter block ending early on a line that merely starts with a dash.
```
---
--count;
---
```
#11403 8f7786f Thanks @Princesseuh! - Fixed the children of an Astro element carrying is:raw being parsed as markup instead of raw text. This now also covers <script> and <style>, whose contents Astro emits verbatim rather than processing, so they are no longer linted as JavaScript or CSS.
```
<article is:raw><% awesome %></article>
<script is:raw>{{ mustache }}</script>
```
#11403 8f7786f Thanks @Princesseuh! - Fixed Astro rejecting attribute names that start with a colon, such as :href.
#11403 8f7786f Thanks @Princesseuh! - Fixed the Astro parser failing to recover from a malformed closing tag such as <div></{<//, so that a later mistake is reported where it happens rather than cascading.
#11403 8f7786f Thanks @Princesseuh! - Fixed { inside an Astro <math> element opening an expression. MathML is foreign content where Astro parses no expressions, so LaTeX such as R^{2x} now survives as text. <svg> is unaffected.
#11403 8f7786f Thanks @Princesseuh! - Fixed {{ at the start of an Astro expression being read as an interpolation. Astro has no {{ }} syntax, so {{ a: 1 }} and <Comp a={{ b: 1 }} /> are object literals.
#11403 8f7786f Thanks @Princesseuh! - Fixed expressions inside an Astro <pre> or <textarea> being read as raw text. Astro parses both as ordinary elements, so their markup and interpolations are now parsed, and a variable used only inside one is no longer reported as unused.
```
<pre>{value}</pre>
<textarea><div>{value}</div></textarea>
```
#11403 8f7786f Thanks @Princesseuh! - Added support for template literal attribute values in Astro, such as <div class=`a ${b} c`>.
#11403 8f7786f Thanks @Princesseuh! - Fixed Astro rejecting HTML5 unquoted attribute values that contain `, =, ' or ", such as <a href=a=b> and <a href=a'b>.
#11393 [dec5a8f](ht

✂ Note

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

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.

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

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.

Poem

🐇 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.
✨

🚥 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

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

_{Comment @coderabbitai help to get the list of available commands.}

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

faab705

Uh oh!

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.5.12

Patch Changes

v2.5.11

Patch Changes

v2.5.10

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!

Reviews paused

Walkthrough

Changes

Estimated code review effort

Possibly related issues

Poem

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

renovate Bot commented Feb 21, 2026 •

edited

Loading

`v2.5.12`

`v2.5.11`

`v2.5.10`

coderabbitai Bot commented May 14, 2026 •

edited

Loading

konard commented Jun 19, 2026 •

edited

Loading

konard commented Jun 19, 2026 •

edited

Loading