feat: Add view.render op

[alexander-alderman-webb]

Description

The view.render op is documented in the devdocs https://github.com/getsentry/sentry-docs/blob/b97ca94a50e4bc9f4380e559af077db89a802a84/develop-docs/sdk/telemetry/traces/span-operations.mdx#L119

Add the op so view.response.render set by the Django integration can be deprecated in favor of view.render.

PR Checklist

• I have run yarn test and verified that the tests pass.
• I have run yarn generate to generate and format code and docs.

If an attribute was added:

• The attribute is in a namespace (e.g. nextjs.function_id, not function_id)
• I have used the correct value for apply_scrubbing (i.e. manual or auto. Use never only for values that should never be scrubbed such as IDs)

If an attribute was deprecated:

• I've followed the policies described in CONTRIBUTING.md

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-conventions	Ready	Preview	Oct 12, 2026 11:27am UTC

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• Add view.render op by alexander-alderman-webb in #699

---

_{🤖 This preview updates automatically when you update the PR.}

[Lms24]

Fair. Was thinking for a moment if ui.render should replace it but that's rather frontend-centered, so for rendering a view in the backend, I'm fine with view.render.