[Snyk] Upgrade @segment/analytics-next from 1.53.0 to 1.72.1 #2265
Conversation
This file contains 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
Snyk has created this PR to upgrade @segment/analytics-next from 1.53.0 to 1.72.1. See this package in npm: @segment/analytics-next See this project in Snyk: https://app.snyk.io/org/nexuscompute/project/a5f4a7d5-d399-47c5-b53e-e7f88d184f74?utm_source=github&utm_medium=referral&page=upgrade-pr
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.
Snyk has created this PR to upgrade @segment/analytics-next from 1.53.0 to 1.72.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 24 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: @segment/analytics-next
-
1.72.1 - 2024-07-18
- #1115
-
1.72.0 - 2024-07-15
- #1107
-
1.71.0 - 2024-07-11
- #1101
- #1100
- #1101
-
1.70.0 - 2024-05-22
- #1088
- #1090
- Do not expose loadLegacySettings / loadCDNSettings (private API)
-
1.69.0 - 2024-04-29
- #1080
- Updated dependencies [
- @ segment/analytics-core@1.6.0
-
1.68.0 - 2024-04-24
-
1.67.0 - 2024-04-12
-
1.66.0 - 2024-03-06
-
1.64.0 - 2024-02-05
-
1.63.0 - 2024-01-10
-
1.62.1 - 2024-01-08
-
1.62.0 - 2023-11-29
-
1.61.0 - 2023-11-15
-
1.60.0 - 2023-11-13
-
1.59.0 - 2023-10-24
-
1.58.0 - 2023-10-09
-
1.57.0 - 2023-10-02
-
1.56.0 - 2023-09-21
-
1.55.0 - 2023-09-08
-
1.54.0 - 2023-08-28
-
1.53.4 - 2023-08-22
-
1.53.3 - 2023-08-03
-
1.53.2 - 2023-07-27
-
1.53.1 - 2023-07-17
-
1.53.0 - 2023-06-07
from @segment/analytics-next GitHub release notesPatch Changes
73ac593Thanks @ silesky! - Update argument resolver to user interface rather than full UserMinor Changes
91e72baThanks @ silesky! - Vendor tsub.js 2.0.0Minor Changes
aee18d2Thanks @ silesky! - Export segment plugin and arg resolverse60f625Thanks @ danieljackins! - Flush large keepalive requestsPatch Changes
aee18d2Thanks @ silesky! - Add edgeFunction to CDNSettings typeMinor Changes
2299e9aThanks @ silesky! - Refactor to change interface name fromlegacySettings->cdnSettings, in order to clarify code.b611746Thanks @ silesky! - - Add public settings APIMinor Changes
e884b61Thanks @ silesky! - Addresses an issue where, if one of the non-destination actions fails to load/is blocked, the entire SDK fails to load. This is most notable in GA4, where, if GA was blocked, Segment initialization would fail.Patch Changes
e884b61,e884b61]:Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: