Repository navigation
build(deps)!: develop against Effect 4.1.2 - #39
Draft
relsunkaev wants to merge 4 commits into
Draft
relsunkaev wants to merge 4 commits into
relsunkaev wants to merge 4 commits into
Conversation
Migrate migration hashing to Digest and provide the Node digest layer at runtime assembly. Keep the checksum encoding and line-ending normalization unchanged. BREAKING CHANGE: effect-db requires Effect >=4.1.2 <4.2.0. Effect-based migration readers now require Digest.Digest from effect/crypto rather than Crypto.Crypto; provide NodeCrypto.layerDigest. The CLI and Promise APIs provide it automatically. effect-qb retains its Effect 4.0 minimum.
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.
Develop against Effect 4.1.2. 15 files changed; local gates and all seven CI jobs pass. Draft awaiting merge approval; no release or merge.
Why
Problem: development still used Effect 4.0, while 4.1 moved the Crypto API.
Key Changes
Dependency upgrade:
>=4.1.2 <4.2.0for effect-db.>=4.0.0 <4.2.0for effect-qb.Native crypto migration:
Compatibility proof:
Risks & Testing Needed
Breaking change: effect-db drops Effect 4.0 support.
→ Effect-based migration readers now need
Digest.Digestfromeffect/crypto; provideNodeCrypto.layerDigestalongside platform services.Unchanged: CLI and Promise APIs provide the services automatically. effect-qb keeps its 4.0 minimum.
Not tested locally: Node 22 and 26.
→ All Node 22/24/26 verification and integration CI jobs passed on 5186197.
Verification note: an overlapping local package rebuild invalidated the first integration run. A serialized rerun passed all 197 tests without a product workaround.
Build status: all seven CI jobs passed; local build, 741 tests, types, packed consumers, layout checks, and 197 integration tests passed on Node 24.22.1.
Test Plan
bun install --frozen-lockfile bun run build bun test --coverage bun run test:types bun run test:pack bun run test:integrationRollback
Before merge, closing this draft leaves main and published packages unchanged.
After merge, revert the upgrade PR before another release.