Sourced from @​sentry/browser's releases.

7.81.0

Important Changes

- feat(nextjs): Add instrumentation utility for server actions (#9553)

This release adds a utility function withServerActionInstrumentation to the @sentry/nextjs SDK for instrumenting your Next.js server actions with error and performance monitoring.

You can optionally pass form data and headers to record them, and configure the wrapper to record the Server Action responses:

import * as Sentry from "@sentry/nextjs";
import { headers } from "next/headers";
export default function ServerComponent() {
async function myServerAction(formData: FormData) {
"use server";
return await Sentry.withServerActionInstrumentation(
"myServerAction", // The name you want to associate this Server Action with in Sentry
{
formData, // Optionally pass in the form data
headers: headers(), // Optionally pass in headers
recordResponse: true, // Optionally record the server action response
},
async () => {
// ... Your Server Action code
    return { name: "John Doe" };
  }
);

}
return (
<form action={myServerAction}>
<input type="text" name="some-input-value" />
<button type="submit">Run Action</button>
</form>
);
}

Other Changes

• docs(feedback): Example docs on sendFeedback (#9560)
• feat(feedback): Add level and remove breadcrumbs from feedback event (#9533)
• feat(vercel-edge): Add fetch instrumentation (#9504)
• feat(vue): Support Vue 3 lifecycle hooks in mixin options (#9578)
• fix(nextjs): Download CLI binary if it can't be found (#9584)
• ref: Deprecate extractTraceParentData from @sentry/core & downstream packages (#9158)
• ref(replay): Add further logging to network body parsing (#9566)

... (truncated)

Sourced from @​sentry/browser's changelog.

7.81.0

Important Changes

- feat(nextjs): Add instrumentation utility for server actions (#9553)

This release adds a utility function withServerActionInstrumentation to the @sentry/nextjs SDK for instrumenting your Next.js server actions with error and performance monitoring.

You can optionally pass form data and headers to record them, and configure the wrapper to record the Server Action responses:

import * as Sentry from "@sentry/nextjs";
import { headers } from "next/headers";
export default function ServerComponent() {
async function myServerAction(formData: FormData) {
"use server";
return await Sentry.withServerActionInstrumentation(
"myServerAction", // The name you want to associate this Server Action with in Sentry
{
formData, // Optionally pass in the form data
headers: headers(), // Optionally pass in headers
recordResponse: true, // Optionally record the server action response
},
async () => {
// ... Your Server Action code
    return { name: "John Doe" };
  }
);

}
return (
<form action={myServerAction}>
<input type="text" name="some-input-value" />
<button type="submit">Run Action</button>
</form>
);
}

Other Changes

• docs(feedback): Example docs on sendFeedback (#9560)
• feat(feedback): Add level and remove breadcrumbs from feedback event (#9533)
• feat(vercel-edge): Add fetch instrumentation (#9504)
• feat(vue): Support Vue 3 lifecycle hooks in mixin options (#9578)
• fix(nextjs): Download CLI binary if it can't be found (#9584)
• ref: Deprecate extractTraceParentData from @sentry/core & downstream packages (#9158)
• ref(replay): Add further logging to network body parsing (#9566)

... (truncated)

• 2f364fe release: 7.81.0
• feeb70a Merge pull request #9596 from getsentry/prepare-release/7.81.0
• 4ff96ec meta(changelog): Update changelog for 7.81.0
• 6f4edf8 feat(vue): Support Vue 3 lifecycle hooks in mixin options (#9578)
• ff416ae feat(vercel-edge): Add fetch instrumentation (#9504)
• 1e2bf6e ref(tracing-internal): Export fetch instrumentation (#9473)
• f48b697 dev: Add missing --sig arg to yalc:publish task (#9511)
• 13aaf3c feat(feedback): Add level and remove breadcrumbs from feedback event (#9533)
• ed2b201 fix(nextjs): Download CLI binary if it can't be found (#9584)
• 5698094 ref(replay): Add further logging to network body parsing (#9566)
• Additional commits viewable in compare view

Sourced from @​sentry/tracing's releases.

7.81.0

Important Changes

- feat(nextjs): Add instrumentation utility for server actions (#9553)

This release adds a utility function withServerActionInstrumentation to the @sentry/nextjs SDK for instrumenting your Next.js server actions with error and performance monitoring.

You can optionally pass form data and headers to record them, and configure the wrapper to record the Server Action responses:

import * as Sentry from "@sentry/nextjs";
import { headers } from "next/headers";
export default function ServerComponent() {
async function myServerAction(formData: FormData) {
"use server";
return await Sentry.withServerActionInstrumentation(
"myServerAction", // The name you want to associate this Server Action with in Sentry
{
formData, // Optionally pass in the form data
headers: headers(), // Optionally pass in headers
recordResponse: true, // Optionally record the server action response
},
async () => {
// ... Your Server Action code
    return { name: "John Doe" };
  }
);

}
return (
<form action={myServerAction}>
<input type="text" name="some-input-value" />
<button type="submit">Run Action</button>
</form>
);
}

Other Changes

• docs(feedback): Example docs on sendFeedback (#9560)
• feat(feedback): Add level and remove breadcrumbs from feedback event (#9533)
• feat(vercel-edge): Add fetch instrumentation (#9504)
• feat(vue): Support Vue 3 lifecycle hooks in mixin options (#9578)
• fix(nextjs): Download CLI binary if it can't be found (#9584)
• ref: Deprecate extractTraceParentData from @sentry/core & downstream packages (#9158)
• ref(replay): Add further logging to network body parsing (#9566)

... (truncated)

Sourced from @​sentry/tracing's changelog.

7.81.0

Important Changes

- feat(nextjs): Add instrumentation utility for server actions (#9553)

This release adds a utility function withServerActionInstrumentation to the @sentry/nextjs SDK for instrumenting your Next.js server actions with error and performance monitoring.

You can optionally pass form data and headers to record them, and configure the wrapper to record the Server Action responses:

import * as Sentry from "@sentry/nextjs";
import { headers } from "next/headers";
export default function ServerComponent() {
async function myServerAction(formData: FormData) {
"use server";
return await Sentry.withServerActionInstrumentation(
"myServerAction", // The name you want to associate this Server Action with in Sentry
{
formData, // Optionally pass in the form data
headers: headers(), // Optionally pass in headers
recordResponse: true, // Optionally record the server action response
},
async () => {
// ... Your Server Action code
    return { name: "John Doe" };
  }
);

}
return (
<form action={myServerAction}>
<input type="text" name="some-input-value" />
<button type="submit">Run Action</button>
</form>
);
}

Other Changes

• docs(feedback): Example docs on sendFeedback (#9560)
• feat(feedback): Add level and remove breadcrumbs from feedback event (#9533)
• feat(vercel-edge): Add fetch instrumentation (#9504)
• feat(vue): Support Vue 3 lifecycle hooks in mixin options (#9578)
• fix(nextjs): Download CLI binary if it can't be found (#9584)
• ref: Deprecate extractTraceParentData from @sentry/core & downstream packages (#9158)
• ref(replay): Add further logging to network body parsing (#9566)

... (truncated)

• 2f364fe release: 7.81.0
• feeb70a Merge pull request #9596 from getsentry/prepare-release/7.81.0
• 4ff96ec meta(changelog): Update changelog for 7.81.0
• 6f4edf8 feat(vue): Support Vue 3 lifecycle hooks in mixin options (#9578)
• ff416ae feat(vercel-edge): Add fetch instrumentation (#9504)
• 1e2bf6e ref(tracing-internal): Export fetch instrumentation (#9473)
• f48b697 dev: Add missing --sig arg to yalc:publish task (#9511)
• 13aaf3c feat(feedback): Add level and remove breadcrumbs from feedback event (#9533)
• ed2b201 fix(nextjs): Download CLI binary if it can't be found (#9584)
• 5698094 ref(replay): Add further logging to network body parsing (#9566)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions