-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
meta: Update Changelog for 8.37.0 #14184
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
Merged
Merged
Conversation
This file contains hidden or 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
While working on the plugin to auto instrument the server I noticed that running SolidStart in spa mode (`ssr: false`) behaved slightly differently so I added a test app for this.
[Gitflow] Merge master into develop
We test lower versions in e2e tests, so we can bump to reasonably newer versions where possible in the package itself.
…14147) Add a general escape hatch for the browser extension detection check in favour of further bloating the bundle size by introducing more special cases in the extension check. This way, we still initially block `Sentry.init` and make users think twice how to proceed. However, we don't have to adapt the check every time a false positive gets reported.
…e spans (#14056) Add the `deliveryType` field of a `ResourcePeformanceEntry` to our `op: resource` spans. This [attribute](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/deliveryType) can give a definitive answer if a resource was retrieved from the browser cache or if the request was actually made to the resource src.
We are not using them, so no need to include them. If/when we decide to use this again we can re-add them (in a current version). Also resolves a security warning for outdated marked dependency.
fix(astro): `waitUntil` flush at end of request
Bump some transitive dev dependencies to hopefully resolve (not actionable, but still) security warnings: * http-cache-semantics * mout * node-forge * chalk/ansi-regex * node-fetch * marked * send * serve-static
feat(nuxt): Add `entrypointWrappedFunctions` to define async wrapped server functions
After reverting #14134, this is a more bundle-size friendly way of adding monitoring for Pinia in Nuxt. The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, add the `piniaIntegration` to your client config: ```ts // sentry.client.config.ts import { usePinia } from '#imports'; Sentry.init({ integrations: [ Sentry.piniaIntegration(usePinia(), { /* optional Pinia plugin options */ }), ], });
Co-authored-by: Francesco Novy <[email protected]>
resolves #12500 resolves #14165 `modulesIntegration` uses top-level require which will crash ESM apps if you explicitly import and use the integration. ```mjs // index.mjs Sentry.init({ dsn: '__DSN__', integrations: [ Sentry.modulesIntegration(), ] }); ``` This fixes that by adding a boolean check for cjs apps, and logging out a warning as a result.
The metrics beta has ended, so we are deprecating the metrics API. 🫡
Fixed one typo and then found another, and another… Most of these aren't exactly critical as they're mostly in comments/tests, but some are in TSDocs and package descriptions which might be nice to get fixed. Co-authored-by: Sigrid Huemer <[email protected]>
Removes VS Code workspace settings that imo are more preference than adding anything useful.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #14144 Co-authored-by: AbhiPrasad <[email protected]>
…arent span (#14183) - check for the start time stamp and drops long task spans starting before a _navigation_ spans started. - refactor the start and end logic a bit to compensate for bundle size increase (see comment) - add a regression test that previously would fail
3db0c5a
to
ad42711
Compare
size-limit report 📦
|
andreiborza
approved these changes
Nov 5, 2024
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.
No description provided.