Version Packages#13
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
093b2b6 to
adcf6d9
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 publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@segment/analytics-next@1.84.0
Minor Changes
#1342
65951526Thanks @MichaelGHSeg! - Unify and harden HTTP response handling and retry behavior across browser and node SDKs.Browser (
@segment/analytics-next) - Add config-driven response handling for Segment.io delivery (httpConfigwith rate-limit/backoff controls). - Improve batching/dispatcher retry semantics for 429 and transient failures. - Use configuredprotocolfor batching requests whenapiHosthas no scheme, while preserving compatibility forapiHostvalues that already includehttp://orhttps://.Node (
@segment/analytics-node) - Align publisher retry/status behavior with updated response handling rules. - AddmaxTotalBackoffDurationandmaxRateLimitDurationsettings to control retry ceilings. - Update default retry configuration to increase resilience under transient failures.Core (
@segment/analytics-core) - Standardize backoff defaults used by retry queues.Patch Changes
65951526]: