chore(deps): update all dependencies#296
Conversation
📝 WalkthroughSummary by CodeRabbitПримечания к выпуску
WalkthroughОбновлены devDependency-версии в трёх package.json: ИзмененияОбновление зависимостей
Оценка затрат на проверку кода🎯 1 (Trivial) | ⏱️ ~2 minutes Возможно связанные issues
Возможно связанные PR
Рекомендуемые рецензенты
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/all
branch
from
d92da30 to
4aec7e9
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 `@packages/lib/package.json`:
- Around line 77-82: The package.json dependency updates (notably "fast-check"
-> v4 and "jscpd") lack a linked specification/issue and migration details;
create or attach an issue/PR description that explains the reason for each
dependency bump (reference "fast-check" and "jscpd" from package.json), include
a checklist of migration steps performed for fast-check v4, document test
results (including running "bun run test" across all packages), and provide a
brief risk/impact analysis of breaking changes from jscpd and fast-check; update
the PR to link this issue and confirm tests pass before merging.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 822cae1a-ef62-4f28-806c-36490725ff83
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (3)
packages/app/package.jsonpackages/docker-git-session-sync/package.jsonpackages/lib/package.json
📜 Review details
⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
- GitHub Check: E2E (Clone auto-open SSH)
- GitHub Check: E2E (Login context)
- GitHub Check: E2E (Browser command)
- GitHub Check: Test
- GitHub Check: E2E (Clone cache)
- GitHub Check: E2E (Runtime volumes + SSH)
- GitHub Check: Lint
- GitHub Check: E2E (OpenCode)
- GitHub Check: Final build (windows-latest)
🧰 Additional context used
📓 Path-based instructions (1)
**/*
⚙️ CodeRabbit configuration file
**/*: Ты строгий ревьюер SPEC DRIVEN DEVELOPMENT.Перед выводами изучи README.md, другие *.md файлы, linked issues,
PR description, PR comments/discussion и релевантную кодовую базу.Сверь изменения с исходным ТЗ/спекой и обсуждением. Флагай любой уход
от спеки, недокументированное изменение поведения, отсутствие тестов
для заявленного поведения и security-риск. Если спека не видна,
попроси автора добавить ее в issue или PR description.Проверь решение с точки зрения формальной верификации: какие инварианты,
предусловия и постусловия можно доказать математически, а где доказуемость
слабая. Оцени решение с точки зрения теории игр: устойчивы ли стимулы,
нет ли выгодного обхода правил, и какое решение было бы сильнее.
Files:
packages/docker-git-session-sync/package.jsonpackages/lib/package.jsonpackages/app/package.json
🔇 Additional comments (5)
packages/lib/package.json (3)
82-82: Версия vite 8.0.13 существует и доступна в npm registry. Зависимость валидна.
80-80: Проверьте документацию breaking changes в jscpd 4.2.0 перед внедрением.jscpd версия 4.2.0 существует, однако документированные breaking changes о Vue SFC tokenization и custom tokenizer backend не подтверждены в публичной документации. Проект активно использует jscpd через
/* jscpd:ignore-* */директивы в 150+ файлах, но не имеет явной.jscpdконфигурации. Перед тем как заявлять о breaking changes, уточните в CHANGELOG или官方 документации какие именно изменения влияют на текущую конфигурацию проекта и требуют миграции.
77-77: 🏗️ Heavy liftОбновление fast-check v3→v4 корректно применено и совместимо с существующим кодом.
Хотя это мажорное обновление, используемые API (fc.assert, fc.property, fc.string, fc.constantFrom, fc.option, fc.record, fc.tuple, fc.oneof) остаются стабильными в v4. Проверка кодовой базы показала:
- Отсутствие использования deprecated API (например, withDeletedKeys)
- Единственное использование fc.record — простая структура без breaking changes
- Все тесты проходят в CI pipeline, что свидетельствует об успешной миграции
Обновление вместе с jscpd (^4.1.1 → ^4.2.0) и vite (^8.0.12 → ^8.0.13) является плановым обновлением зависимостей.
packages/app/package.json (2)
122-122: Версия vite 8.0.13 существует в npm registry и доступна для использования. Никаких проблем не выявлено.
119-119: Версия совместима — Vue в проекте не используется.jscpd 4.2.0 упоминаемые breaking changes для Vue SFC токенизации не применимы к данному проекту, так как в нём нет файлов
.vue. Версия 4.2.0 соответствует требованиям vibecode-linter (^4.0.5), который использует jscpd как runtime dependency для детекции дублирования кода.> Likely an incorrect or invalid review comment.
| "fast-check": "^4.8.0", | ||
| "@vitest/eslint-plugin": "^1.6.17", | ||
| "globals": "^17.6.0", | ||
| "jscpd": "^4.1.1", | ||
| "jscpd": "^4.2.0", | ||
| "typescript": "^6.0.3", | ||
| "vite": "^8.0.12", | ||
| "vite": "^8.0.13", |
There was a problem hiding this comment.
Отсутствует спецификация для обновления зависимостей.
Согласно coding guidelines, необходима спецификация/issue для всех изменений: "Сверь изменения с исходным ТЗ/спекой и обсуждением. Флагай любой уход от спеки... Если спека не видна, попроси автора добавить ее в issue или PR description."
Для мажорного обновления fast-check (v3→v4) с breaking changes особенно важно иметь:
- Linked issue с обоснованием обновления
- Чек-лист выполненных миграционных шагов
- Подтверждение прохождения тестов
- Оценку рисков breaking changes
Пожалуйста, создайте или привяжите issue с описанием:
- Причины обновления каждой зависимости
- Выполненных миграционных шагов для fast-check v4
- Результатов тестирования (включая
bun run testво всех пакетах) - Анализа влияния breaking changes jscpd на проект
🤖 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 `@packages/lib/package.json` around lines 77 - 82, The package.json dependency
updates (notably "fast-check" -> v4 and "jscpd") lack a linked
specification/issue and migration details; create or attach an issue/PR
description that explains the reason for each dependency bump (reference
"fast-check" and "jscpd" from package.json), include a checklist of migration
steps performed for fast-check v4, document test results (including running "bun
run test" across all packages), and provide a brief risk/impact analysis of
breaking changes from jscpd and fast-check; update the PR to link this issue and
confirm tests pass before merging.
1 participant
This PR contains the following updates:
^3.23.2→^4.8.0^4.1.1→^4.2.0^8.0.12→^8.0.13cc @skulidropek
Release Notes
dubzzz/fast-check (fast-check)
v4.8.0Compare Source
New arbitrary to chain in a loop fashion
[Code][Diff]
Features
chainUntilarbitrary for iterative chainingFixes
skipLibCheck$CLAUDE_PROJECT_DIRdiscussions: writeto release jobs\p{...}value drift in docs testsv4.7.0Compare Source
Unicode property support in
stringMatching[Code][Diff]
Features
jsonarbitrary\p{}and\P{}instringMatching\p{UnicodeProperty}instringMatchingstringMatchingFixes
make_latest?rawimports for adventsv4.6.0Compare Source
Better
stringMatchingwithmaxLength[Code][Diff]
Features
maxLengthsupport tostringMatchingmaxLengthonstringMatchingRandom::next(n)andRandom::nextInt()Fixes
fast-checkusingrolldownpermissions: {}to workflows missing itflatMapwithchainin error messagev4.5.3Compare Source
Proper attestation file naming
[Code][Diff]
Fixes
v4.5.2Compare Source
Attach tarballs to GitHub releases
[Code][Diff]
Fixes
v4.5.1Compare Source
Rename tarballs before publishing
[Code][Diff]
Fixes
v4.5.0Compare Source
Add an arbitrary based on a schema definition
[Code][Diff]
Features
entityGraphfor schema-based structuresentityGraphentityGraphentityGraphentityGraphentityGraphentityGraphFixes
entityGraphdocumentationentityGraphentityGraphinto sub-helpersv4.4.0Compare Source
Expose hidden arbitraries and widen capabilities of existing ones from a typing point of view
[Code][Diff]
Features
PropertyKeyinfc.dictionary(...)fc.maparbitrarycircularoption tofc.letrecfc.setarbitraryletrecFixes
@traversable/zod-testto ecosystemletrecimplementationsletrecLazyArbitraryv4.3.0Compare Source
Add memory flag on
infiniteStream[Code][Diff]
Features
Fixes
fc.optionnil frequencyignoredBuiltDependenciesv4.2.0Compare Source
New primitives for race condition detection
[Code][Diff]
Features
actschedulerwaitIdle, a revampedwaitAllforschedulerwaitOneandwaitAllFixes
v4.1.1Compare Source
Avoid overlapping tasks
[Code][Diff]
Fixes
schedulerexecutionschedulerwith explicitundefinedcheckv4.1.0Compare Source
More effective
waitForonfc.scheduler[Code][Diff]
Features
waitForFixes
waitForwaitForon interactions with micro-tasksv4.0.1Compare Source
Change location of the logo on the README for LFS quotas reasons
[Code][Diff]
Fixes
v4.0.0Compare Source
Reducing the API surface to ease ramp-up on fast-check
[Code][Diff]
The simplest migration guide to v4 is probably here.
Breaking changes
.noBiasuuidVarbitraryunicodeJson*arbitrariesuuidto build any know versionascii*hexa*base64stringOfchar16bitsandstring16bitsfullUnicode*unicode*charbig{U|}int{N|}nextArrayIntfromRandom.noShrinkFeatures
constantFromconstantArbitrary<XxxArray>=>Arbitrary<XxxArray<ArrayBuffer>>fc.recordFixes
scheduleSequencejsonnoBiasisolatedDeclarationsflag on the projectnode --runwithDeletedKeysfromrecordrun{Before/After}Eachon propertytypespec-fast-checkto ecosystem pageBigIntcheck inmixedCasescheduleSequencetypeofchecksobjectand relateddoublescheduleSequenceObject.assignBigIntin testskucherenko/jscpd (jscpd)
v4.2.0Compare Source
Breaking Changes
.vuefiles are no longer tokenized asmarkup. Each block is now dispatched to its own sub-format:<script>→javascript,<script lang="ts">→typescript,<template>→markup,<style>→css,<style lang="scss">→scss,<style lang="less">→less. Clone reports for.vuefiles now appear under these resolved sub-format names. Any tooling or configuration that relied on.vueclones being reported undermarkupmust be updated.--formatsExtsusers — custom mappings that pointed.vuetomarkup(e.g."formatsExts": { "markup": ["vue"] }) will no longer take effect because.vueis handled by the dedicatedvueformat processor. Remove or update such mappings.New Features
prismjsnpm package with a self-contained reprism-based grammar engine. ~11.5% faster tokenization on real projects (avg 1126 ms → 997 ms on a 548-file, 223-format scan)..vue), Svelte (.svelte), Astro (.astro), and Markdown files are now tokenized per-block/per-section. A<script>block in a.vuefile can match a.tsfile; a fenced code block in Markdown can match a.pyfile./usr/bin/env python3) are auto-detected by their#!shebang line and tokenized in the correct language.--store-path— configure a custom directory for the LevelDB cache, eliminating collisions when multiple jscpd processes run in parallel on the same machine.--skipComments— shorthand flag for--mode weak, which strips comments before detection.--formats-names— map specific filenames (e.g.Makefile,Dockerfile) to a detection format.Bug Fixes
@jscpd/core#728) — RabinKarp flushed the pending clone on a store hit at end-of-file instead of on a miss. Files that are complete copies of each other were undetected. Fixed.@jscpd/tokenizer#737) — the Lisp string regex/"(?:[^"\\]*|\\.)*"/could catastrophically backtrack (O(2ⁿ)) on unterminated strings. Replaced with a linear/"(?:[^"\\]|\\[\s\S])*"/pattern.package.json(#739) —readJSONSyncthrew an unhandledSyntaxErrorwhenpackage.jsoncontained invalid JSON, killing the process. Now emits a warning and continues with an empty config.vue) as the store namespace for all SFC blocks, preventing a<script>block in one.vuefile from ever matching a<script>block in another. The namespace now reflects each block's resolved sub-format.@jscpd/tokenizer.Known Limitations
vitejs/vite (vite)
v8.0.13Compare Source
Features
onEnd(#22357) (47071ce)Bug Fixes
write=false(#22328) (158e8ae)name/originalFileNamein syntheticassetFileNamescall (#22439) (8e59c97)isBundledper environment (#22257) (a576326)Miscellaneous Chores
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.