[spider4] Update snyk 1.1064.0 → 1.1291.0 (minor) #4737
Closed
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ snyk (1.1064.0 → 1.1291.0) · Repo
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 11 commits:
chore: curate RELEASE_NOTES (#5209)Merge pull request #5200 from snyk/hotfix/v1.1290.0-dverbose-cyclic-fixfix: support cyclic dependencies in maven with dverbosechore: Merge pull request #5193 from snyk/fix/CLI-287_release_stepsfix(ci): add deployment steps to release brancheschore: Merge pull request #5185 from snyk/tmp/1713542475-release-candidatedocs: update release noteschore: merge main into release-candidate Fri Apr 19 18:03:04 CEST 2024feat(ci): First release on stable channel (#5183)fix(ci): Adapt script to work on different environments (#5182)chore(ci): Enable preview and stable deployments (#5178)🆕 @sentry-internal/tracing (added, 7.112.2)
🆕 @sentry/core (added, 7.112.2)
🆕 @sentry/integrations (added, 7.112.2)
🆕 @sentry/node (added, 7.112.2)
🆕 @sentry/types (added, 7.112.2)
🆕 @sentry/utils (added, 7.112.2)
🆕 boolean (added, 3.2.0)
🆕 define-data-property (added, 1.1.4)
🆕 define-properties (added, 1.2.1)
🆕 detect-node (added, 2.1.0)
🆕 es-define-property (added, 1.0.0)
🆕 es-errors (added, 1.3.0)
🆕 es6-error (added, 4.1.1)
🆕 escape-string-regexp (added, 4.0.0)
🆕 function-bind (added, 1.1.2)
🆕 get-intrinsic (added, 1.2.4)
🆕 global-agent (added, 3.0.0)
🆕 globalthis (added, 1.0.4)
🆕 gopd (added, 1.0.1)
🆕 has-property-descriptors (added, 1.0.2)
🆕 has-proto (added, 1.0.3)
🆕 has-symbols (added, 1.0.3)
🆕 hasown (added, 2.0.2)
🆕 immediate (added, 3.0.6)
🆕 lie (added, 3.1.1)
🆕 localforage (added, 1.10.0)
🆕 lru-cache (added, 6.0.0)
🆕 matcher (added, 3.0.0)
🆕 object-keys (added, 1.1.1)
🆕 roarr (added, 2.15.4)
🆕 semver (added, 7.6.0)
🆕 semver-compare (added, 1.0.0)
🆕 serialize-error (added, 7.0.1)
🆕 sprintf-js (added, 1.1.3)
🆕 type-fest (added, 0.13.1)
🆕 yallist (added, 4.0.0)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands