-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat(deps): update sentry-javascript monorepo #481
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/sentry-javascript-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
BundleMonFiles updated (1)
Unchanged files (40)
Total files change +11.16KB +0.17% Groups updated (1)
Unchanged groups (2)
Final result: ✅ View report in BundleMon website ➡️ |
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
July 31, 2023 22:27
195cee2
to
dcb28ae
Compare
renovate
bot
changed the title
feat(deps): update dependency @sentry/react to v7.57.0
feat(deps): update dependency @sentry/react to v7.61.0
Jul 31, 2023
renovate
bot
changed the title
feat(deps): update dependency @sentry/react to v7.61.0
feat(deps): update dependency @sentry/react to v7.66.0
Aug 31, 2023
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 31, 2023 23:02
dcb28ae
to
7a6c89b
Compare
renovate
bot
changed the title
feat(deps): update dependency @sentry/react to v7.66.0
feat(deps): update dependency @sentry/react to v7.72.0
Oct 1, 2023
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
October 1, 2023 01:54
7a6c89b
to
be9afeb
Compare
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
November 1, 2023 01:54
be9afeb
to
e47cbb0
Compare
renovate
bot
changed the title
feat(deps): update dependency @sentry/react to v7.72.0
feat(deps): update dependency @sentry/react to v7.77.0
Nov 1, 2023
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
December 1, 2023 00:50
e47cbb0
to
bccb8ee
Compare
renovate
bot
changed the title
feat(deps): update dependency @sentry/react to v7.77.0
feat(deps): update dependency @sentry/react to v7.84.0
Dec 1, 2023
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 1, 2024 01:46
bccb8ee
to
b571688
Compare
renovate
bot
changed the title
feat(deps): update dependency @sentry/react to v7.84.0
feat(deps): update sentry-javascript monorepo to v7.91.0
Jan 1, 2024
renovate
bot
changed the title
feat(deps): update sentry-javascript monorepo to v7.91.0
feat(deps): update sentry-javascript monorepo to v7.99.0
Feb 1, 2024
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 1, 2024 02:08
b571688
to
cfd77b2
Compare
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 1, 2024 01:41
cfd77b2
to
ec0bb22
Compare
renovate
bot
changed the title
feat(deps): update sentry-javascript monorepo to v7.99.0
feat(deps): update sentry-javascript monorepo to v7.104.0
Mar 1, 2024
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 1, 2024 01:59
ec0bb22
to
b631354
Compare
renovate
bot
changed the title
feat(deps): update sentry-javascript monorepo to v7.104.0
feat(deps): update sentry-javascript monorepo to v7.109.0
Apr 1, 2024
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
April 30, 2024 22:35
b631354
to
d3537f2
Compare
renovate
bot
changed the title
feat(deps): update sentry-javascript monorepo to v7.109.0
feat(deps): update sentry-javascript monorepo to v7.112.2
Apr 30, 2024
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
May 31, 2024 22:01
d3537f2
to
b4307bd
Compare
renovate
bot
changed the title
feat(deps): update sentry-javascript monorepo to v7.112.2
feat(deps): update sentry-javascript monorepo
May 31, 2024
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
August 1, 2024 00:51
b4307bd
to
d2b3cc6
Compare
renovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
September 1, 2024 01:00
d2b3cc6
to
87fba28
Compare
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 contains the following updates:
7.88.0
->7.114.0
7.88.0
->7.119.0
Release Notes
getsentry/sentry-javascript (@sentry/integrations)
v7.114.0
Compare Source
Important Changes
This release fixes a bug that caused the cumulative layout shift (CLS) web vital not to be reported in a majority of the
cases where it should have been reported. With this change, the CLS web vital should now always be reported for
pageloads with layout shift. If a pageload did not have layout shift, no CLS web vital should be reported.
Please note that upgrading the SDK to this version may cause data in your dashboards to drastically change.
Other Changes
tunnel
support to multiplexed transport (#11851)HTTP_REQUEST_METHOD
attribute (#11929)v7.113.0
Compare Source
Important Changes
This release adds support for Node 22! 🎉
It also adds prebuilt-binaries for Node 22 to
@sentry/profiling-node
.Other Changes
v7.112.2
Compare Source
browserTracingIntegration
(#11765)v7.112.1
Compare Source
v7.112.0
Compare Source
Important Changes
Instead of installing
@sentry/integrations
, you can now import the pluggable integrations directly from your SDKpackage:
Note that only the functional integrations (e.g.
xxxIntegration()
) are re-exported.Other Changes
Bundle size 📦
v7.111.0
Compare Source
server.address
to browserhttp.client
spans (#11663)browserTracingIntegration
(#11647)Bundle size 📦
v7.110.1
Compare Source
tunnelRoute
matching logic for hybrid cloud (#11577)Bundle size 📦
v7.110.0
Compare Source
Important Changes
You can now use a
interactionsSampleRate
to control the sample rate of INP spans.interactionsSampleRate
is appliedon top of the global
tracesSampleRate
. Therefore ifinteractionsSampleRate
is0.5
andtracesSampleRate
is0.1
,then the actual sample rate for interactions is
0.05
.This release deprecates the
Hub
class, as well as theaddRequestDataToTransaction
method. ThetrpcMiddleware
method is no longer on the
Handlers
export, but instead is a standalone export.Please see the detailed Migration docs on how to migrate to the new APIs.
trpcMiddleware
(#11389)Hub
class (#11528)Hub
interface (#11530)addRequestDataToTransaction
(#11368)Other Changes
OPTIONS
andHEAD
request. (#11485)statsd
tometric_bucket
(#11505)Bundle size 📦
v7.109.0
Compare Source
This release deprecates some exports from the
@sentry/replay
package. These exports have been moved to the browser SDK(or related framework SDKs like
@sentry/react
).rrweb
to 2.12.0 (#11317)@sentry/replay
exports (#11242)Work in this release contributed by @soerface. Thank you for your contribution!
Bundle size 📦
v7.108.0
Compare Source
This release fixes issues with Time to First Byte (TTFB) calculation in the SDK that was introduced with
7.95.0
. Italso fixes some bugs with Interaction to First Paint (INP) instrumentation. This may impact your Sentry Performance
Score calculation.
ResizeObserver
andgoogletag
default filters (#11210)cron
(#11225)sampled
type onTransaction
(#11146)Work in this release contributed by @quisido and @joshkel. Thank you for your contributions!
Bundle size 📦
v7.107.0
Compare Source
This release fixes issues with INP instrumentation with the Next.js SDK and adds support for the
enableInp
option inthe deprecated
BrowserTracing
integration for backwards compatibility.handled
value in ErrorBoundary depending on fallback [v7] (#11037)Bundle size 📦
v7.106.1
Compare Source
createReduxEnhancer
on server (#11010)Bundle size 📦
v7.106.0
Compare Source
tunnelRoute
option (#10958)setTransactionName
global
(#10925)AttachmentType
and use for envelopeattachment_type
property (#10946)Work in this release contributed by @jessezhang91 and @bfontaine. Thank you for your contributions!
Bundle size 📦
v7.105.0
Compare Source
Important Changes
withActiveSpan
is exported everywhere (#10877)You can use the
withActiveSpan
method to ensure a certain span is the active span in a given callback. This can beused to create a span as a child of a specific span with the
startSpan
API methods:Bundle size 📦
v7.104.0
Compare Source
Important Changes
This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
is released with the upcoming
24.3.0
release of self-hosted.To opt-in to this feature, you can use the
enableInp
option in thebrowserTracingIntegration
:Other Changes
nodeProfilingIntegration
(#10864)errorHandler
for replayCanvas integration (#10796)Bundle size 📦
v7.103.0
Compare Source
Important Changes
forceTransaction
tostartSpan()
APIs (#10819)You can now pass
forceTransaction: true
tostartSpan()
,startSpanManual()
andstartInactiveSpan()
. This allowsyou to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to
the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if
possible, ensuring it shows up as a transaction throughout the system.
Please note that setting this to
true
does not guarantee that this will be sent as a transaction, but that the SDKwill try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it
in the Sentry UI.
Other Changes
Bundle size 📦
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.