Version Packages#377
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
0469d6e to
4d90e91
Compare
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
@vercel/flags-core@1.5.0
Minor Changes
#371
bd4d01aThanks @vincent-derks! - Add jitter to ingest retries and the batch-flush window.The usage tracker now uses AWS-style "Full Jitter" exponential backoff between
retry attempts (replacing the previous deterministic 100/200ms schedule) and
randomizes the 5s batch-flush window by ±20% to desynchronize concurrent
processes. When all retry attempts are exhausted the SDK now logs a structured
warning so consumers can alert on dropped batches.
Patch Changes
#382
4d90e91Thanks @dferber90! - Speed up flag evaluation on the hot path.handleOutcomeno longer recomputesscaledWeightson every split-outcome evaluation; the per-outcome scaled weights are cached on first call.matchConditionsno longer recompilesRegExpon every REGEX / NOT_REGEX condition; the compiled regex is cached on first call.Controller.read()andgetDatafile()no longer re-destructure and re-spread the in-memory datafile on every call; the result is cached and rebuilt only when stream/poll replaces the underlying data.In micro-benchmarks the pure
evaluate()path is ~22% faster for split outcomes and ~32% faster for regex conditions. The fullclient.evaluate()path is 14–22% faster across all scenarios.@flags-sdk/vercel@1.3.1
Patch Changes
4d90e91,bd4d01a]: