ci: Version Packages - #248
Merged
Merged
Conversation
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tanstack/angular-pacer@0.24.0
Minor Changes
Patch Changes
dc47121,dc47121,dc47121,bd96217,dc47121]:@tanstack/pacer@0.22.0
Minor Changes
Patch Changes
fix(queuer): stop silently dropping falsy items (
0,'',false) from AsyncQueuer processing, and stop throwing a TypeError whennullitems are added to AsyncQueuer or Queuer without a customgetPriority(fixes #200) (#246)fix(async-queuer): respect the
waitperiod whenaddItemis called during active processing.pendingTicknow stays true while executions or wait timers are pending (matching the sync Queuer's semantics), task errors no longer kill the processing chain or produce unhandled promise rejections during tick-driven processing, andflush/flushAsBatchrestart the tick chain they interrupt (fixes #188) (#246)fix: async utility return types no longer double-wrap promises.
maybeExecute,flush,lastResultstate, andonSuccesscallbacks on AsyncDebouncer, AsyncThrottler, and AsyncRateLimiter (and theasyncDebounce/asyncThrottle/asyncRateLimithelpers) now useAwaited<ReturnType<TFn>>instead ofReturnType<TFn>. TheuseAsyncDebouncedCallback,useAsyncThrottledCallback, anduseAsyncRateLimitedCallbackhooks in react-pacer and preact-pacer now returnPromise<Awaited<ReturnType<TFn>> | undefined>, matching the angular adapter and the actual runtime behavior (fixes #156) (#246)fix: remove the devtools event-client integration from AsyncRetryer to fix unbounded memory growth (AsyncQueuer leaks memory in Node.js via unintended retryer key propagation #198). Retryer instances are created per-execution by AsyncQueuer, AsyncDebouncer, AsyncThrottler, and AsyncRateLimiter, so every execution permanently accumulated a devtools event listener, a live instance in the devtools registry (keyed
"<key>-retryer-N", or"undefined-retryer-N"when the parent had no key), and queued devtools events — most visibly as a memory leak in Node.js. The devtools panel never consumed retryer events, so no devtools functionality is lost. Thekeyoption on AsyncRetryer remains as a plain identifier, and internal retryers now receiveasyncRetryerOptionsunmodified (#246)@tanstack/pacer-devtools@1.4.0
Minor Changes
@tanstack/preact-pacer@0.23.0
Minor Changes
Patch Changes
fix: async utility return types no longer double-wrap promises.
maybeExecute,flush,lastResultstate, andonSuccesscallbacks on AsyncDebouncer, AsyncThrottler, and AsyncRateLimiter (and theasyncDebounce/asyncThrottle/asyncRateLimithelpers) now useAwaited<ReturnType<TFn>>instead ofReturnType<TFn>. TheuseAsyncDebouncedCallback,useAsyncThrottledCallback, anduseAsyncRateLimitedCallbackhooks in react-pacer and preact-pacer now returnPromise<Awaited<ReturnType<TFn>> | undefined>, matching the angular adapter and the actual runtime behavior (fixes #156) (#246)Updated dependencies [
dc47121,dc47121,dc47121,bd96217,dc47121]:@tanstack/preact-pacer-devtools@0.7.0
Minor Changes
Patch Changes
bd96217]:@tanstack/react-pacer@0.23.0
Minor Changes
Patch Changes
fix: async utility return types no longer double-wrap promises.
maybeExecute,flush,lastResultstate, andonSuccesscallbacks on AsyncDebouncer, AsyncThrottler, and AsyncRateLimiter (and theasyncDebounce/asyncThrottle/asyncRateLimithelpers) now useAwaited<ReturnType<TFn>>instead ofReturnType<TFn>. TheuseAsyncDebouncedCallback,useAsyncThrottledCallback, anduseAsyncRateLimitedCallbackhooks in react-pacer and preact-pacer now returnPromise<Awaited<ReturnType<TFn>> | undefined>, matching the angular adapter and the actual runtime behavior (fixes #156) (#246)Updated dependencies [
dc47121,dc47121,dc47121,bd96217,dc47121]:@tanstack/react-pacer-devtools@0.8.0
Minor Changes
Patch Changes
bd96217]:@tanstack/solid-pacer@0.22.0
Minor Changes
Patch Changes
dc47121,dc47121,dc47121,bd96217,dc47121]:@tanstack/solid-pacer-devtools@0.7.0
Minor Changes
Patch Changes
bd96217]: