Release Notes

This update provides important internal improvements and security upgrades.

Internal

Adds the following configuration options to the Sentry backend integration:
- profile_lifecycle = "trace": In trace mode, the profiler starts and stops automatically based on active spans: the profiler continues to run while there is at least one active span, and stops when there are no active spans.
- enable_logs = True: Enables Sentry structured logs, allowing you to use the sentry_sdk.logger APIs to send logs to Sentry. This option must be set to True to automatically capture logs from Python’s built-in logging module or other supported logging integrations.
Sentry release tags follow Sentry's preferred SemVer Version formatting, e.g. pingpong@6.0+800.
The auto-incrementing commit number in the commit tag is used as the build number, e.g. build 809 from tag 809-srv383-web238.
The release workflow will fail if the release name does not follow PingPong's SemVer Version formatting (v<major>.<minor>.<patch?>-<prerelease?>). This change prevents issues where the commit tag name is used as a release name, which is GitHub's default.
Sentry releases are correctly tagged with "staging" or "production" environments.
Bump vite from 7.0.7 to 7.0.8 in /web/study in the npm_and_yarn group across 1 directory

Schema Upgrade	Migration Script	Permissions Update	Task Definition Update	Configuration Update
No	No	No	No	No

internal/ Upgrade Sentry backend config by @ekassos in #1047
workflows/ Change Sentry release version by @ekassos in #1048
Bump vite from 7.0.7 to 7.0.8 in /web/study in the npm_and_yarn group across 1 directory by @dependabot[bot] in #1046

Full Changelog: 808-srv382-web238...810-srv383-web239