-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
meta(changelog): Update changelog for 8.23.0 #13228
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
Reverting the change in this PR: #13138 For the time being (until this is debugged and fixed), this change is reverted and the Nuxt module will still be built with the nuxt-module-builder. The changed build-setup led to an error in `nuxt dev` and the navigation in the E2E test apps did not work. The error message: ``` ERROR [worker reload] [worker init] Package import specifier "#internal/nitro/virtual/app-config" is not defined in package /Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/nitropack/package.json imported from /Users/sigridh/Documents/DEV/sentry-javascript-examples/node_modules/nitropack/dist/runtime/config.mjs ``` Similar errors were reported here: - nuxt/content#2736 - nuxt/icon#204 - nuxt/nuxt#13801
Add a `getTraceData` function to the `@sentry/core` package and re-exports it in none-browser SDKs inheriting from it. --------- Co-authored-by: Andrei <[email protected]>
Upgrade action to artifacts v4 (previous version did some convenient merging for us)
Our playwright tests can be flakey caused by the build process when generating static assets. Even though we check if file exists before symlinking, it can at times fail because file already exists. I have not dug/thought about why this happens -- just catch/ignore and move on. Closes #11902
This PR adds instrumentation for the [`scheduled` handler](https://developers.cloudflare.com/workers/runtime-apis/handlers/scheduled/) in cloudflare workers. This is used for cron triggers. I elected to not do automatic cron instrumentation for now. Instead I added manual instrumentation docs to the README, this will get copied to the sentry docs eventually.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #13062 Co-authored-by: Lms24 <[email protected]>
…AndRenderDialog (#13203) This PR updates `_loadAndRenderDialog` to call `dialog.close()` in the `onFormClose` and `onFormSubmitted` callbacks.
…13192) While working on adding the cloudflare sdk to some open source projects, I noticed that setup for the cloudflare plugin was a bit of a hassle when you needed access to environmental variables. This PR allows users to pass a function to `sentryPagesPlugin` that looks like so: ```ts handler: (context: EventPluginContext<Env, Params, Data, PluginParams>) => CloudflareOptions ``` This means that users can access the cloudflare `context` (which only exists at the request level) to get environmental variables. ```javascript export const onRequest = Sentry.sentryPagesPlugin(context => ({ dsn: context.env.SENTRY_DSN, tracesSampleRate: 1.0, })); ``` To make some other use cases easier, this PR also exposes the `wrapRequestHandler` API to users.
This test is quite flakey -- most of the time it correctly has the image as LCP, but sometimes it will report the button as LCP. I have tried fixing it by waiting for image to load, but it did not work. I wonder if it is a bug with our LCP reporting?
…distributed tracing (#13221) Works by adding the Sentry middlware to your `src/middleware.ts` file: ```typescript import { sentryBeforeResponseMiddleware } from '@sentry/solidstart/middleware'; import { createMiddleware } from '@solidjs/start/middleware'; export default createMiddleware({ onBeforeResponse: [ sentryBeforeResponseMiddleware(), // Add your other middleware handlers after `sentryBeforeResponseMiddleware` ], }); ``` And specifying `./src/middleware.ts` in `app.config.ts` Closes: #12551 Co-authored-by: Lukas Stracke <[email protected]>
The file implementing the nest integration in node got a bit annoying to work with, so splitting it up.
Nuxt is using the Vue router under the hood, but the previous condition to detect a page load (`from.name == null && from.matched.length === 0`) does not work with Nuxt, as `from.matched` is never empty.
…#13202) Co-authored-by: Charly Gomez <[email protected]> Co-authored-by: Luca Forstner <[email protected]>
Lms24
approved these changes
Aug 5, 2024
size-limit report 📦
|
s1gr1d
approved these changes
Aug 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.