ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

ref(flags/v8): rename unleash integration param - #15344

Closed
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8
Closed

ref(flags/v8): rename unleash integration param#15344
aliu39 wants to merge 101 commits into
developfrom
aliu/unleash-param-v8

Conversation

@aliu39

@aliu39aliu39 commented Feb 7, 2025

Copy link
Copy Markdown
Member

(Accidentally pointed at v8)

mydeaand others added 30 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.
Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)
We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)
This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.
Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)
Backport of #14753:
Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.
See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.
This is to take advantage of the following change in 5.22.0:
> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].
There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):
> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.
The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766
---------
Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)
Backport of #14778
---------
Co-authored-by: Artur <arthurandrosovich@gmail.com>
The v8 suffixed layer lands in the release-registry every time we
publish a release from the v8 branch which not only breaks
https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253
but also ends up in the docs as the current version: when using the ARN
dropdown
https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/.
This removes the suffix so we get the current major published under the
non-suffixed name.
Follow-up task:
#14842
Lms24and others added 27 commits January 27, 2025 10:29
backport of #15139
---------
Co-authored-by: Randolf J <34705014+jrandolf@users.noreply.github.com>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
It _seems_ we've got way more flakes since 18.20.6 was released, let's
see if this fixes this possibly...
Backport
This also needs to go into v8, I guess!
---------
Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Backport of #15161
---------
Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
Co-authored-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com>
backport of #15171
Co-authored-by: chris-basebone <100691954+chris-basebone@users.noreply.github.com>
…rumentation (#15237)
backport of #15235 and #15241
---------
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is
merged.
---------
Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Add a guard to the Svelte SDK's component update tracking feature
to catch an error thrown by Svelte 5 in Runes mode. In Runes mode,
components must not call the old `beforeUpdate` or `afterUpdate`
lifecycle hooks.
@aliu39
aliu39 requested review from a team as code ownersFebruary 7, 2025 21:04
@aliu39aliu39 closed this Feb 7, 2025
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@aliu39@mydea@andreiborza@getsentry-bot@timfish@AbhiPrasad@s1gr1d@Lms24@chargome@onurtemizkan@nwalters512