Repository navigation
build(deps): effect 4.1.0 and @effect/tsgo 0.63.0 - #359
Merged
Merged
Conversation
Move effect and every @effect/* to 4.1.0 and @effect/tsgo to 0.63.0 (oxlint ~1.90.0, oxlint-tsgolint 7.0.2005, which tsgo 0.63 requires). effect 4.1.0 removed effect/Crypto, which the published stryker-js and stryker-js-vitest-runner import: migrate to effect/crypto/SecureRandom and Digest, brand Schema classes, register the MCP toolkit through the stdio transport, and regenerate the published contract documents. Claude-Session: https://claude.ai/code/session_017rX35xUAHEjVVaDKVVzubW
…unds effect 4.1.0 writes the safe-integer range onto integer fields in the generated stream schema. The contract version law counts that as a breaking stream change, so the stream version moves to 9.0 and cli-contract takes a major changeset. Claude-Session: https://claude.ai/code/session_017rX35xUAHEjVVaDKVVzubW
…rning the rule off Revert the oxlint override entries that switched effecttsgo/unstable-api-usage off and list the unstable modules each package imports in the tsgo plugin's allowedUnstableApis. Claude-Session: https://claude.ai/code/session_017rX35xUAHEjVVaDKVVzubW
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrades effect and every @effect/* to 4.1.0 and @effect/tsgo to 0.63.0 (catalog and the two packages' exact pins). oxlint moves to ~1.90.0 and oxlint-tsgolint to 7.0.2005, the pair tsgo 0.63.0 supports. pnpm
overridesmap@effect/opentelemetry,@effect/platform-node,@effect/platform-node-sharedand@effect/tsgoto the catalog so the released tarballs do not pull a second copy;pnpm why effectshows only 4.1.0.This unblocks mutation testing on effect 4.1.0. The published
@systemfsoftware/stryker-js17.0.2 and@systemfsoftware/stryker-js-vitest-runner8.1.1 importeffect/Crypto, which effect 4.1.0 removed, so a run fails with ERR_MODULE_NOT_FOUND on any repo that has moved to 4.1.0. This change migrates the source toeffect/crypto/SecureRandomandDigest(NodeCrypto.layerSecureRandom/layerDigest), and a changeset releases a patch of the eight published packages. The effect peer range becomes^4.1.0, becauseeffect/crypto/*does not exist in 4.0.x.Code changes the upgrade required:
effect/Cryptotoeffect/crypto/*in stryker-js (node-platform.ts), stryker-js-vitest-runner, test/e2e and test/bench;randomUUIDv4touuidV4(),digesttodigestHex.{ readonly brand: unique symbol }argument (tsgoschemaClassMissingBrand); the places that built them from plain objects now call.make. The sandbox script keeps its plain namespace record withOmit<..., 'brand'>.McpServer.layerStdio({ registrations }), with a middleware that provides the engine services to each request (4.1 makes tooldependenciesrequest-level).FileSystem.File.Infodev/inoare bigint: the case-sensitivity probe and its property test useS.BigInt.Report.MutationScore.matchlost its explicit generic;CliErrorgainedValidationErrorin checker-parity.namerename it (mutatorName,entryName,errorName), pererrorPayloadShadowsName.Effect.flatten,Effect.as,Effect.tap,Effect.trackSuccesses/trackErrors, a singleEffect.provide.isFinitechecks).allowedUnstableApis(tsconfig). The nine pre-existingunstable-api-usage: offlines are untouched.Stream version: effect 4.1.0 writes the safe-integer range onto integer fields of the generated stream schema; the repo's contract version law counts that as breaking, so the run stream moves 8.0 to 9.0 and
stryker-js-cli-contracttakes a major changeset. Needs the owner's eye.Known: the two typescript-checker integration tests that import
EngineandWorkerfrom the released stryker-js tarball (.sfs-deps, pinned by thestryker-publishedflake input) cannot load under effect 4.1.0 until the release from this change is published and the pin moves.Local: lint, lint:tsgo, typecheck and build pass in all 24 packages; plugin-interface and cli-contract tests pass after regenerating the contracts.
https://claude.ai/code/session_017rX35xUAHEjVVaDKVVzubW