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
fix(deps): update gatsby (major) #1230
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-gatsby
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
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.
Open
+6,524
−5,714
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1230 +/- ##
=======================================
Coverage 83.61% 83.61%
=======================================
Files 64 64
Lines 1422 1422
Branches 311 311
=======================================
Hits 1189 1189
Misses 232 232
Partials 1 1 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
4 times, most recently
from
March 10, 2023 06:53
b12a39c
to
5cb29ef
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
from
March 21, 2023 12:03
5cb29ef
to
f6693f7
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
7 times, most recently
from
March 30, 2023 10:17
70a052b
to
cfb2ce0
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
from
April 5, 2023 02:48
cfb2ce0
to
7e15e42
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
2 times, most recently
from
April 25, 2023 12:44
a8f8eaf
to
069d9c6
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
from
May 1, 2023 21:39
069d9c6
to
161fa93
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
4 times, most recently
from
May 16, 2023 01:25
43c8e69
to
d734d59
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
2 times, most recently
from
May 22, 2023 20:11
7dc247b
to
de3a0d1
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
2 times, most recently
from
June 6, 2023 01:16
7008806
to
dfdd989
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
4 times, most recently
from
June 15, 2023 16:18
d217fff
to
6092bd0
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
2 times, most recently
from
November 22, 2023 12:05
56c790c
to
4f365d9
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
from
December 7, 2023 15:13
4f365d9
to
8553b24
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
5 times, most recently
from
December 23, 2023 07:03
2265fb1
to
9413769
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
2 times, most recently
from
December 30, 2023 07:04
943b989
to
29f1484
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
4 times, most recently
from
January 27, 2024 01:23
8ac5d34
to
c82d9dd
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
from
March 19, 2024 22:01
c82d9dd
to
46dd26e
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
2 times, most recently
from
April 11, 2024 22:33
8227af9
to
6988c09
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
6 times, most recently
from
May 19, 2024 15:15
4c656d9
to
7520ad9
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
5 times, most recently
from
May 25, 2024 04:20
1120639
to
5b43e5a
Compare
renovate
bot
force-pushed
the
renovate/major-gatsby
branch
from
May 25, 2024 18:13
5b43e5a
to
961c2ee
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.61.1
->^8.4.0
^4.25.9
->^5.13.5
^4.25.0
->^5.13.1
^4.25.0
->^5.13.1
^4.25.0
->^5.13.1
^4.25.0
->^5.13.1
^2.25.0
->^3.13.1
^4.25.0
->^5.13.1
^5.25.0
->^6.13.2
^5.25.0
->^6.13.1
^4.25.1
->^5.13.1
^5.25.0
->^6.13.1
^5.25.0
->^6.13.1
^5.25.0
->^6.13.1
^6.25.0
->^7.13.1
^6.25.0
->^7.13.1
^5.25.0
->^6.13.1
^5.25.0
->^6.13.1
^4.25.0
->^5.13.1
^5.25.1
->^6.13.1
^4.25.0
->^5.13.1
Release Notes
getsentry/sentry-javascript (@sentry/gatsby)
v8.4.0
Compare Source
Important Changes
If you are using Next.js version
14.3.0-canary.64
or above, the Sentry Next.js SDK will now trace clientside pageloadswith React Server Components. This means, that client-side errors like
Error: An error occurred in the Server Components render.
, which previously didn't give you much information on howthat error was caused, can now be traced back to a specific error in a server component.
This release guarantees support for Angular 18 with
@sentry/angular
.Other Changes
v8.3.0
Compare Source
Important Changes
This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.
feat(node): Ensure connect spans have better data (#12130)
feat(node): Ensure express spans have better data (#12107)
feat(node): Ensure fastify spans have better data (#12106)
feat(node): Ensure hapi spans have better data (#12140)
feat(node): Ensure koa spans have better data (#12108)
feat(node): Ensure Nest.js spans have better data (#12139)
feat(deps): Bump @opentelemetry/instrumentation-express from 0.38.0 to 0.39.0 (#12079)
feat(node): No-code init via
--import=@​sentry/node/init
(#11999)When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:
When using CommonJS, you can do:
Other Changes
browserProfilingIntegration
is published to CDN (#12158)node:
prefix for node built-ins (#11895)setTimeout
to avoid e.g. angular change detection (#11924)undefined
values in props (#12131)@prisma/instrumentation
from 5.13.0 to 5.14.0 (#12081)Work in this release contributed by @pboling. Thank you for your contribution!
v8.2.1
Compare Source
v8.2.0
Compare Source
beforeSendSpan
hook (#11886)Scope
(#12067)hasTracingEnabled()
if possible (#12066)v8.1.0
Compare Source
This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we
updated some initially missed points in our migration guides and documentation.
lastEventId
on isolation scope (#11951) (#12022)awslambda-auto
parseSampleRate
utility function (#12024)eventId
optional and uselastEventId
in report dialog (#12029)v8.0.0
Compare Source
Important Changes
The Bun SDK will now capture global unhandled errors.
Other Changes
http.client
spans if there is an active parent span (#11974)execArgv
are not sent to worker threads (#11963)v7.116.0
Compare Source
This release publishes a new AWS Lambda layer under the name
SentryNodeServerlessSDKv7
that users still running v7 canuse instead of pinning themselves to
SentryNodeServerlessSDK:235
.Bundle size 📦
v7.115.0
Compare Source
start()
(#12003)lastEventId
deprecation warnings (#12042)Bundle size 📦
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 📦
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.