build(deps-dev): bump fast-check from 3.23.2 to 4.9.0 - #2158
Conversation
jbeckwith-oai
left a comment
There was a problem hiding this comment.
Requesting changes for two branch-specific regressions at this exact head. The functional suite otherwise passes on Node 22/24/26, including the fast-check property tests, and the upstream runtime/type floors, package integrity, provenance, and advisory state are compatible. Please address the inline blockers.
853f2fe to
93f2a62
Compare
93f2a62 to
5b63d76
Compare
jbeckwith-oai
left a comment
There was a problem hiding this comment.
Two blockers remain at this refreshed exact head. First, fast-check v4 exposes , , and as named exports, so both lint and detect-breaking-changes fail on the existing namespace import in ; please migrate those calls to named imports. Second, the lockfile still refreshes unrelated and Vite/postcss entries even though fast-check v4 depends only on pure-rand; please keep this dependency PR scoped to the fast-check/pure-rand closure. The functional Node 22/24/26 suite otherwise passes.
Bumps [fast-check](https://github.com/dubzzz/fast-check/tree/HEAD/packages/fast-check) from 3.23.2 to 4.9.0. - [Release notes](https://github.com/dubzzz/fast-check/releases) - [Changelog](https://github.com/dubzzz/fast-check/blob/main/packages/fast-check/CHANGELOG.md) - [Commits](https://github.com/dubzzz/fast-check/commits/v4.9.0/packages/fast-check) --- updated-dependencies: - dependency-name: fast-check dependency-version: 4.9.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
5b63d76 to
df381f9
Compare
jbeckwith-oai
left a comment
There was a problem hiding this comment.
The unrelated lockfile churn from the prior head is fixed: this diff is now scoped to fast-check and its pure-rand dependency. One compatibility blocker remains, however. fast-check v4 exposes assert, property, and json as named exports, while tests/_vendor/partial-json-parser/partial-json-parsing.test.ts still imports the default fc object and accesses those members through it. That makes both the required lint and detect-breaking-changes checks fail with six import/no-named-as-default-member errors. Please migrate these uses to named imports (or an equally lint-clean v4-compatible form). The build, examples, ecosystem tests, and Node 22/24/26 functional suites pass at this exact head.
Bumps fast-check from 3.23.2 to 4.9.0.
Release notes
Sourced from fast-check's releases.
... (truncated)
Changelog
Sourced from fast-check's changelog.
... (truncated)
Commits
0d3c254🔖 Update CHANGELOG.md for fast-check@4.9.0,@fast-check/packaged@0.7.1 (#7124)bd85efe⬆️ Update dependency@types/nodeto ^24.13.3 (#7118)a0596ab⬆️ Update dependency vitest to ^4.1.10 (#7119)3c085da⬆️ Update dependency prettier to v3.9.4 (#7114)6538ff0👥 Add jneidel as doc contributor (#7108)8096ab0👥 Add makeeno as doc contributor (#7104)13fd4a6✏️ Typo in typeEntityGraphContraints(#7088)36e70d2⬆️ Update dependency@microsoft/api-extractorto ^7.58.9 (#7080)451ede0⬆️ Update dependency vitest to ^4.1.8 (#7074)949564d⚡️ Early exit on empty tuple infc.entityGraph(#7071)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for fast-check since your current version.