Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the sentry group across 1 directory with 2 updates #1107

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 14, 2024

Bumps the sentry group with 2 updates in the / directory: @sentry/cli and @sentry/node.

Updates @sentry/cli from 2.35.0 to 2.37.0

Release notes

Sourced from @​sentry/cli's releases.

2.37.0

All Xcode uploads are now executed in the foreground, which should allow for easier debugging of any problems that occur while uploading files during the build process, since errors will be logged directly within Xcode.

With this change, the --force-foreground flag is no longer needed, since we always upload in the foreground. The flag is now a deprecated no-op.

2.36.6

There are no code changes in this release. It is being performed to test an update to the release build process.

2.36.5

There are no code changes in this release. It is a re-release of 2.36.4, which we are making because 2.36.4 and 2.36.3 failed to publish to PyPI.

2.36.4

This releases fixes includes a bugfix (#2171 by @​szokeasaurusrex) for #2169. The bug caused any command run with sentry-cli monitors run to not be executed whenever sending the cron checkin to Sentry failed, e.g. during a Sentry outage or due to some other network failure. With the bugfix, we log the error and execute the program even when there was an error sending the checkin.

We recommend that all users using sentry-cli monitors run upgrade to Sentry CLI version 2.36.4 immediately.

2.36.3

Various fixes & improvements

2.36.2

Various fixes & improvements

2.36.1

Various fixes & improvements

  • Fix a bug where background Xcode uploads sometimes failed

2.36.0

Various fixes & improvements

  • Log when file not added to source bundle (#2146) by @​szokeasaurusrex
  • Bump Symbolic to 12.11.0. This fixes a bug where uploading source files sometimes failed when any of the files were not UTF-8 encoded
Changelog

Sourced from @​sentry/cli's changelog.

2.37.0

All Xcode uploads are now executed in the foreground, which should allow for easier debugging of any problems that occur while uploading files during the build process, since errors will be logged directly within Xcode.

With this change, the --force-foreground flag is no longer needed, since we always upload in the foreground. The flag is now a deprecated no-op.

2.36.6

There are no code changes in this release. It is being performed to test an update to the release build process.

2.36.5

There are no code changes in this release. It is a re-release of 2.36.4, which we are making because 2.36.4 and 2.36.3 failed to publish to PyPI.

2.36.4

This releases fixes includes a bugfix (#2171 by @​szokeasaurusrex) for #2169. The bug caused any command run with sentry-cli monitors run to not be executed whenever sending the cron checkin to Sentry failed, e.g. during a Sentry outage or due to some other network failure. With the bugfix, we log the error and execute the program even when there was an error sending the checkin.

We recommend that all users using sentry-cli monitors run upgrade to Sentry CLI version 2.36.4 immediately.

2.36.3

Various fixes & improvements

2.36.2

Various fixes & improvements

2.36.1

Various fixes & improvements

  • Fix a bug where background Xcode uploads sometimes failed

2.36.0

Various fixes & improvements

  • Log when file not added to source bundle (#2146) by @​szokeasaurusrex
  • Bump Symbolic to 12.11.0. This fixes a bug where uploading source files sometimes failed when any of the files were not UTF-8 encoded
Commits

Updates @sentry/node from 8.28.0 to 8.34.0

Release notes

Sourced from @​sentry/node's releases.

8.34.0

Important Changes

  • ref(nextjs): Remove dead code (#13828)

Relevant for users of the @sentry/nextjs package: If you have previously configured a SENTRY_IGNORE_API_RESOLUTION_ERROR environment variable, it is now safe to unset it.

Other Changes

  • feat(cdn): Export getReplay in replay CDN bundles (#13881)
  • feat(replay): Clear fallback buffer when switching buffers (#13914)
  • feat(replay): Upgrade rrweb packages to 2.28.0 (#13732)
  • fix(docs): Correct supported browsers due to globalThis (#13788)
  • fix(nextjs): Adjust path to requestAsyncStorageShim.js template file (#13928)
  • fix(nextjs): Detect new locations for request async storage to support Next.js v15.0.0-canary.180 and higher (#13920)
  • fix(nextjs): Drop _not-found spans for all HTTP methods (#13906)
  • fix(nextjs): Fix resolution of request storage shim fallback (#13929)
  • fix(node): Ensure graphql options are correct when preloading (#13769)
  • fix(node): Local variables handle error (#13827)
  • fix(node): Remove dataloader instrumentation from default integrations (#13873)
  • fix(nuxt): Create declaration files for Nuxt module (#13909)
  • fix(replay): Ensure replay_id is removed from frozen DSC when stopped (#13893)
  • fix(replay): Try/catch sendBufferedReplayOrFlush to prevent cycles (#13900)
  • fix(sveltekit): Ensure trace meta tags are always injected (#13231)
  • fix(sveltekit): Update wrapServerRouteWithSentry to respect ParamMatchers (#13390)
  • fix(wasm): Integration wasm uncaught WebAssembly.Exception (#13787) (#13854)
  • ref(nextjs): Ignore sentry spans based on query param attribute (#13905)
  • ref(utils): Move vercelWaitUntil to utils (#13891)

Work in this release was contributed by @​trzeciak, @​gurpreetatwal, @​ykzts and @​lizhiyao. Thank you for your contributions!

Bundle size 📦

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

8.34.0

Important Changes

  • ref(nextjs): Remove dead code (#13828)

Relevant for users of the @sentry/nextjs package: If you have previously configured a SENTRY_IGNORE_API_RESOLUTION_ERROR environment variable, it is now safe to unset it.

Other Changes

  • feat(cdn): Export getReplay in replay CDN bundles (#13881)
  • feat(replay): Clear fallback buffer when switching buffers (#13914)
  • feat(replay): Upgrade rrweb packages to 2.28.0 (#13732)
  • fix(docs): Correct supported browsers due to globalThis (#13788)
  • fix(nextjs): Adjust path to requestAsyncStorageShim.js template file (#13928)
  • fix(nextjs): Detect new locations for request async storage to support Next.js v15.0.0-canary.180 and higher (#13920)
  • fix(nextjs): Drop _not-found spans for all HTTP methods (#13906)
  • fix(nextjs): Fix resolution of request storage shim fallback (#13929)
  • fix(node): Ensure graphql options are correct when preloading (#13769)
  • fix(node): Local variables handle error (#13827)
  • fix(node): Remove dataloader instrumentation from default integrations (#13873)
  • fix(nuxt): Create declaration files for Nuxt module (#13909)
  • fix(replay): Ensure replay_id is removed from frozen DSC when stopped (#13893)
  • fix(replay): Try/catch sendBufferedReplayOrFlush to prevent cycles (#13900)
  • fix(sveltekit): Ensure trace meta tags are always injected (#13231)
  • fix(sveltekit): Update wrapServerRouteWithSentry to respect ParamMatchers (#13390)
  • fix(wasm): Integration wasm uncaught WebAssembly.Exception (#13787) (#13854)
  • ref(nextjs): Ignore sentry spans based on query param attribute (#13905)
  • ref(utils): Move vercelWaitUntil to utils (#13891)

Work in this release was contributed by @​trzeciak, @​gurpreetatwal, @​ykzts and @​lizhiyao. Thank you for your contributions!

... (truncated)

Commits
  • d7749ae release: 8.34.0
  • 2a1dd9a Merge pull request #13941 from getsentry/prepare-release/8.34.0
  • 20914b0 meta(changelog): Update changelog for 8.34.0
  • 86c626e fix(nextjs): Fix resolution of request storage shim fallback (#13929)
  • fcc3d2b meta(ci): Don't fail CI run when codecov fails to upload (#13930)
  • 0b00605 ci(deps): bump peter-evans/create-pull-request from 6.1.0 to 7.0.5 (#13844)
  • 6b4401f fix(nextjs): Detect new locations for request async storage to support Next.j...
  • 0be3137 fix(nextjs): Adjust path to requestAsynStorageShim.js template file (#13928)
  • d7c33a2 feat(replay): Upgrade rrweb packages to 2.28.0 (#13732)
  • 37b45c1 feat(replay): Clear fallback buffer when switching buffers (#13914)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the sentry group with 2 updates in the / directory: [@sentry/cli](https://github.com/getsentry/sentry-cli) and [@sentry/node](https://github.com/getsentry/sentry-javascript).


Updates `@sentry/cli` from 2.35.0 to 2.37.0
- [Release notes](https://github.com/getsentry/sentry-cli/releases)
- [Changelog](https://github.com/getsentry/sentry-cli/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-cli@2.35.0...2.37.0)

Updates `@sentry/node` from 8.28.0 to 8.34.0
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@8.28.0...8.34.0)

---
updated-dependencies:
- dependency-name: "@sentry/cli"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: sentry
- dependency-name: "@sentry/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: sentry
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 14, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 28, 2024

Superseded by #1132.

@dependabot dependabot bot closed this Oct 28, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/sentry-eefdad5198 branch October 28, 2024 04:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants