Repository navigation
chore(deps): update dependency @effect/tsgo to v0.73.2 - #940
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
renovate
Bot
force-pushed
the
renovate/effect-tsgo-0.x
branch
from
November 20, 2026 02:13
06e9a5e to
e321481
Compare
This branch has not been deployed
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.
This PR contains the following updates:
0.69.0→0.73.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
Effect-TS/tsgo (@effect/tsgo)
v0.73.2Compare Source
Patch Changes
b8ea08c: Fix the intermittent win32-x64 tsrs release build failure "malformed instrumentation profile data: not enough space for another header" / "no profile can be merged". tsrs-test's conformance training runs in many worker processes that all write onesuite-%m.profrawthrough LLVM's online profile merging, which on Windows occasionally leaves the file truncated, andllvm-profdata mergethen rejects the whole merge. The release build now checks every raw profile withllvm-profdata showafter training and, when one is malformed, runs the training again from fresh profiles (up to 3 attempts) instead of failing the job.v0.70.0Compare Source
Minor Changes
9ada5da: Add theflatMapProvideServiceToProvideServiceEffectsuggestion instyle. AnEffect.flatMap(orEffect.andThengiven a callback) whose callback only forwards its parameter toEffect.provideServiceis a manualEffect.provideServiceEffect. The rule reports it in every spelling: pipeable, data-first,pipe(...)and curried, on both the outerflatMapand the innerprovideService, and insideEffect.gen/Effect.fnbodies.A quick fix rewrites the expression to
Effect.provideServiceEffect(self, Key, acquire)and keeps any later pipe steps:Effect.suspend(() => step(s)).pipe(Effect.flatMap((meta) => Effect.provideService(effect, Key, meta)), Effect.map(f))becomesEffect.provideServiceEffect(effect, Key, Effect.suspend(() => step(s))).pipe(Effect.map(f)).The callback is not reported when it does anything else: when the parameter appears outside the service argument (in the program, in any earlier step of the program, or in the key), when the program or key uses something the callback binds (the name of a named function expression, or a function-expression callback's own
this,super,new.targetorarguments, plain or as shorthand{ arguments }), when the service argument is not the bare parameter, when steps followprovideService, when the acquired value's type is not assignable to the key's service type (for example through a(conn: any)parameter), or when theflatMapresult type differs from theprovideServiceEffectone (a return-type annotation on the callback or explicit type arguments that widen it, or explicit type arguments onprovideService), since code after it may rely on that type. After the fix, the program expression is evaluated once when the expression is built rather than on every run of the callback. TheEffect.genform (const p = yield* acquire; return yield* Effect.provideService(self, Key, p)) is deliberately not reported. On Effect v3, data-firstEffect.andThen(acquire, callback)is not reported, since its overloads do not form a dual. The rule supports Effect v3 and v4.Piping-flow fixes can now build an expression for a flow prefix with
PipingFlowPrefixExpression, including prefixes that end inside a.pipe(...)orpipe(...)call.50c28e5: Add theforLoopPushToForEachdiagnostic (style, off by default; enable it with"forLoopPushToForEach": "suggestion") and quickfix. Inside an Effect generator, afor (const x of iterable)loop whose only statement isacc.push(yield* effect), withaccaconst acc = []declared just before the loop, is reported. The fix replaces it withEffect.forEach. The fix is not offered when the accumulator is mutated after the loop, or when the loop binding or the yielded expression contains ayieldof the generator. The callback is passed directly only when it is a plain single-parameter function applied to the loop variable, whether asf(x),pipe(x, f)orx.pipe(f); otherwise an arrow is kept.Patch Changes
75a36b2: Update the TypeScript next tag totypescript@next, which shipstypescript-gocommit6bdcb54d23f41bc7098c1f3488ac599c75b852ca, update the TypeScript beta tag totypescript@beta, and update the TypeScript latest tag totypescript@latest. Refresh the Oxlint configuration schema from the selected package.9ada5da:manualMetricTapToTracknow decides more precisely whether a function-expression callback can become an arrow mapper. It looks for the callback's ownthis,super,new.target,argumentsand name the way the compiler resolves them, through the new typeparser helperUsesFunctionOwnBindings, whichflatMapProvideServiceToProvideServiceEffectnow uses too.The rule now reports callbacks it used to skip, since none of these read a binding of the callback:
It no longer reports a named callback that reads its own name through a shorthand property, which the fix would have left unbound:
Class expressions are still skipped when their
extendsclause, a computed member name or a member decorator reads the callback's bindings.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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.