fix(sentry): emit change-tracking events for v2-versioning environments #11523
gagantrivediAnnotations
11 errors and 3 warnings
|
API Unit Tests (3.13)
Process completed with exit code 2.
|
|
API Unit Tests (3.13):
api/features/models.py#L921
Item "None" of "Environment | None" has no attribute "created_date"
|
|
API Unit Tests (3.13):
api/features/models.py#L920
Item "None" of "Environment | None" has no attribute "use_v2_feature_versioning"
|
|
API Unit Tests (3.11)
The strategy configuration was canceled because "test._3_13" failed
|
|
API Unit Tests (3.11)
Step canceled by GitHub (see: https://depot.dev/docs/github-actions/troubleshooting#error-step-canceled-by-github)
|
|
API Unit Tests (3.11):
api/features/models.py#L921
Item "None" of "Environment | None" has no attribute "created_date"
|
|
API Unit Tests (3.11):
api/features/models.py#L920
Item "None" of "Environment | None" has no attribute "use_v2_feature_versioning"
|
|
API Unit Tests (3.12)
The strategy configuration was canceled because "test._3_13" failed
|
|
API Unit Tests (3.12)
Step canceled by GitHub (see: https://depot.dev/docs/github-actions/troubleshooting#error-step-canceled-by-github)
|
|
API Unit Tests (3.12):
api/features/models.py#L921
Item "None" of "Environment | None" has no attribute "created_date"
|
|
API Unit Tests (3.12):
api/features/models.py#L920
Item "None" of "Environment | None" has no attribute "use_v2_feature_versioning"
|
|
API Unit Tests (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6, liskin/gh-problem-matcher-wrap@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
API Unit Tests (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6, liskin/gh-problem-matcher-wrap@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
API Unit Tests (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6, liskin/gh-problem-matcher-wrap@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|