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

build(deps): bump @sentry/browser from 6.19.7 to 7.21.1 in /scripts/yarn #263

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Nov 24, 2022

Bumps @sentry/browser from 6.19.7 to 7.21.1.

Release notes

Sourced from @​sentry/browser's releases.

7.21.1

  • fix(nextjs): Stop excluding withSentryConfig from serverless bundles (#6267)

7.21.0

  • feat(react): Add tracing support for React Router 6.4 createBrowserRouter. (#6172)
  • fix(core): Add guard against scope.getAttachments (#6258)
  • fix(core): Only generate eventIds in client (#6247)
  • fix(express): Support multiple routers with common paths. (#6253)
  • fix(tracing): Pass tracePropagationTargets to instrumentOutgoingRequests (#6259)

7.20.1

  • fix(angular): Set <unknown> component name default in TraceDirective (#6222)
  • fix(core): Include _sdkProcessingMetadata when cloning scope (#6218)
  • fix(tracing): Make shouldAttachHeaders not fall back to default values (#6238)
  • ref(vue): Check if SDK is initialized before app is mounted (#6227)

7.20.0

  • feat(angular): Add Angular 15 Peer Dependencies (#6220)
  • feat(nextjs): Add excludeServerRoutes config option (#6207)
  • feat(node): Move tracing options to Http integration (#6191)
  • fix(nextjs): Use absolute path for distDir in webpack plugin options (#6214)
  • fix(remix): Resolve Remix Request API compatibility issues. (#6215)
  • ref(nextjs): Invert serverside injection criteria (#6206)

7.19.0

This release adds a new SDK, @​sentry/opentelemetry-node, which is available as an alpha release to integrate OpenTelemetry performance tracing with Sentry. Give it a try and let us know if you have any feedback or problems with using it. (#6000)

This release also deprecates the tracingOrigins option in favor of using shouldCreateSpanForRequest and tracePropagationTargets. See #6176 for details.

  • feat(node): Allow keepAlive override (#6161)
  • feat(tracing): Add transaction.setContext method (#6154)
  • feat(tracing): Allow to set instrumenter on Span & Transaction (#6136)
  • fix(integrations): Remove erroneous WINDOW exports (#6185)
  • fix(react): Guard against non-error obj in ErrorBoundary (#6181)
  • perf(core): Prevent creation of new contexts object on scope (#6156)
  • ref(tracing): Deprecate tracingOrigins (#6176)

7.18.0

This release adds the beforeSendTransaction callback to all JS SDKs, letting you make changes to or drop transactions before they're sent to Sentry. This callback works identically to beforeSend, just for transactions.

  • feat(core): Add beforeSendTransaction (#6121)
  • feat(node): Add option to OnUncaughtException integration that allows mimicking native uncaught error exit behaviour (#6137)
  • feat(tracing): Add tracePropagationTargets option to browser routing instrumentation (#6080)
  • fix(nextjs): Allow onUncaughtException integration to remain excluded (#6148)
  • fix(nextjs): Do not exit process when errors bubble up while additional uncaughtException-handlers are registered (#6138)
  • fix(remix): Prevent capturing pending promises as exceptions. (#6129)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

7.21.1

  • fix(nextjs): Stop excluding withSentryConfig from serverless bundles (#6267)

7.21.0

  • feat(react): Add tracing support for React Router 6.4 createBrowserRouter. (#6172)
  • fix(core): Add guard against scope.getAttachments (#6258)
  • fix(core): Only generate eventIds in client (#6247)
  • fix(express): Support multiple routers with common paths. (#6253)
  • fix(tracing): Pass tracePropagationTargets to instrumentOutgoingRequests (#6259)

7.20.1

  • fix(angular): Set <unknown> component name default in TraceDirective (#6222)
  • fix(core): Include _sdkProcessingMetadata when cloning scope (#6218)
  • fix(tracing): Make shouldAttachHeaders not fall back to default values (#6238)
  • ref(vue): Check if SDK is initialized before app is mounted (#6227)

7.20.0

  • feat(angular): Add Angular 15 Peer Dependencies (#6220)
  • feat(nextjs): Add excludeServerRoutes config option (#6207)
  • feat(node): Move tracing options to Http integration (#6191)
  • fix(nextjs): Use absolute path for distDir in webpack plugin options (#6214)
  • fix(remix): Resolve Remix Request API compatibility issues. (#6215)
  • ref(nextjs): Invert serverside injection criteria (#6206)

7.19.0

This release adds a new SDK, @​sentry/opentelemetry-node, which is available as an alpha release to integrate OpenTelemetry performance tracing with Sentry. Give it a try and let us know if you have any feedback or problems with using it. (#6000)

This release also deprecates the tracingOrigins option in favor of using shouldCreateSpanForRequest and tracePropagationTargets. See #6176 for details.

  • feat(node): Allow keepAlive override (#6161)
  • feat(tracing): Add transaction.setContext method (#6154)
  • feat(tracing): Allow to set instrumenter on Span & Transaction (#6136)
  • fix(integrations): Remove erroneous WINDOW exports (#6185)
  • fix(react): Guard against non-error obj in ErrorBoundary (#6181)
  • perf(core): Prevent creation of new contexts object on scope (#6156)
  • ref(tracing): Deprecate tracingOrigins (#6176)

7.18.0

This release adds the beforeSendTransaction callback to all JS SDKs, letting you make changes to or drop transactions before they're sent to Sentry. This callback works identically to beforeSend, just for transactions.

  • feat(core): Add beforeSendTransaction (#6121)

... (truncated)

Commits
  • 6866161 release: 7.21.1
  • 3bd8da1 meta: Update changelog for 7.21.1 (#6268)
  • b35e3d7 fix(nextjs): Stop excluding withSentryConfig from serverless bundles (#6267)
  • 99864fa Merge branch 'release/7.21.0'
  • 90e53c3 release: 7.21.0
  • 3fbf2a2 chore(otel): Update installation instructions (#6262)
  • 3d9f0fd fix(nextjs): Exclude build-time files from page dependency manifests (#6058)
  • 4ffeedd meta: Update changelog for 7.21.0 (#6260)
  • 3fe5f7a fix(core): Only generate eventIds in client (#6247)
  • 72c6855 fix(express): Support multiple routers with common paths. (#6253)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 6.19.7 to 7.21.1.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@6.19.7...7.21.1)

---
updated-dependencies:
- dependency-name: "@sentry/browser"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Third-party library dependencies. label Nov 24, 2022
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Nov 30, 2022

Superseded by #268.

@dependabot dependabot bot closed this Nov 30, 2022
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/scripts/yarn/sentry/browser-7.21.1 branch November 30, 2022 02:04
nijel added a commit that referenced this pull request Aug 7, 2023
This allows to introduce component categorization in the future, see #263
nijel added a commit that referenced this pull request Aug 7, 2023
This allows to introduce component categorization in the future, see #263
nijel added a commit that referenced this pull request Aug 7, 2023
This allows to introduce component categorization in the future, see #263
nijel added a commit that referenced this pull request Aug 7, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).
nijel added a commit that referenced this pull request Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).
nijel added a commit that referenced this pull request Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).
nijel added a commit that referenced this pull request Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).
nijel added a commit that referenced this pull request Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).
nijel added a commit that referenced this pull request Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

TODO:
Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.

TODO:
Changed object filtering for changes.
- last_changes_url should have just path
- parsing should use path style parsing
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

TODO:
Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.

TODO:
Changed object filtering for changes.
- last_changes_url should have just path
- parsing should use path style parsing
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 10, 2023
Avoid using fixed structure for object URLs. All objects are now
referected as path with possibly variable number of elements. This
allows to introduce component categorization in the future, see #263.

This change also forced change of some URLs which would no longer be
distinguishable (anything under component can no longer have variable
suffix).

Changed widgets URLs to better fit in the new structure. Redirects for
old ones are in place.
nijel added a commit that referenced this pull request Aug 11, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
nijel added a commit that referenced this pull request Aug 11, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
nijel added a commit that referenced this pull request Aug 11, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
- document adjusted  API lookups (category in component, %2F)
nijel added a commit that referenced this pull request Aug 11, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
- document adjusted  API lookups (category in component, %2F)
nijel added a commit that referenced this pull request Aug 12, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
- document adjusted  API lookups (category in component, %2F)
nijel added a commit that referenced this pull request Aug 12, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
- document adjusted  API lookups (category in component, %2F)
nijel added a commit that referenced this pull request Aug 12, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
- document adjusted  API lookups (category in component, %2F)
nijel added a commit that referenced this pull request Aug 14, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
    - tests
    - documentation
nijel added a commit that referenced this pull request Aug 15, 2023
This will make projectlanguge and category work consistently at all
levels.

Issue #263
nijel added a commit that referenced this pull request Aug 16, 2023
This will make projectlanguge and category work consistently at all
levels.

Issue #263
nijel added a commit that referenced this pull request Aug 16, 2023
This will make projectlanguge and category work consistently at all
levels.

Issue #263
nijel added a commit that referenced this pull request Aug 16, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
    - tests
    - documentation
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add category view template
- add UI to:
    - add a category
    - delete a category
    - move component between categories
- add documentation
- add tests
- add API
    - tests
    - documentation
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move a category to another
    - move component between categories
- add documentation
    - API
    - user
- add tests
    - API - create / update / delete
    - UI
        - add
        - browse
        - delete
        - move component to a category
        - rename category
        - move category
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add UI to:
    - add a category
    - delete a category
    - move a category to another
    - move component between categories
- add documentation
    - API
    - user
- add tests
    - API - create / update / delete
    - UI
        - add
        - browse
        - delete
        - move component to a category
        - rename category
        - move category
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add documentation
    - API
    - user
- add tests
    - API - create / update / delete
    - UI
        - add
        - browse
        - delete
        - move component to a category
        - move a category to another
        - rename category
        - move category to another project
        - verify repositories moved together with category
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add documentation
    - API
    - user
- add tests
    - API - create / update / delete
    - UI
        - add
        - browse
        - delete
        - move component to a category
        - move a category to another
        - rename category
        - move category to another project
        - verify repositories moved together with category
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add documentation
    - API
    - user
- add tests
    - API - create / update / delete
    - UI
        - add
        - browse
        - delete
        - move component to a category
        - move a category to another
        - rename category
        - move category to another project
        - verify repositories moved together with category
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add documentation
    - user
- add tests
    - UI
        - add
        - browse
        - delete
        - move component to a category
        - move a category to another
        - rename category
        - move category to another project
        - verify repositories moved together with category
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add tests
    - UI
        - delete
        - move a category to another
        - move category to another project
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263

TODO:

- add tests
    - UI
        - move category to another project
nijel added a commit that referenced this pull request Aug 23, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263
nijel added a commit that referenced this pull request Aug 24, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263
nijel added a commit that referenced this pull request Aug 24, 2023
- add model for storing categories
- browsing of project categories
- support maximal depth of 3 categories rigth now

Fixes #263
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Third-party library dependencies.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants