fix: support non-integer PKs in NotificationMessage (fixes UUID overf… #26730
SchrodingersGatqc_checks.yaml
on: push
Filter
10s
Style [Documentation]
29s
Tests - Migrations [PostgreSQL]
57m 8s
Tests - Full Migration [SQLite]
4m 0s
Style [Typecheck]
2m 19s
Tests - inventree-python
16m 37s
Tests - Performance
12m 27s
Tests - DB [PostgreSQL]
22m 53s
Tests - DB [MySQL]
22m 0s
Security [Zizmor]
Matrix: coverage
Push new schema
0s
Annotations
30 warnings
|
Style [Typecheck]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Style [Typecheck]
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DWUuagAAAACk+fnL3wO0SI+3etMECxBwUEhMMzBFREdFMDExNABFZGdl
|
|
Style [Typecheck]
Failed to restore: Cache service responded with 400
|
|
Tests - API Schema Documentation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - API Schema Documentation
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0FmUuagAAAABiGtgQf2YISaxGp5Q/BmpyTVNQMzExMDAwMTAxMDIzAEVkZ2U=
|
|
Tests - API Schema Documentation
Failed to restore: Cache service responded with 400
|
|
Tests - Full Migration [SQLite]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - Full Migration [SQLite]
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QWUuagAAAADeU/lyBBl0SKvvkB3E8qGnQ0hJMzBFREdFMDIxOQBFZGdl
|
|
Tests - Full Migration [SQLite]
Failed to restore: Cache service responded with 400
|
|
Tests - Performance
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-node@1a4442cacd436585916779262731d5b162bc6ec7, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - Performance
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0pmcuagAAAADYJP/dz8N0R4karsseEQesREIzRURHRTIxMTQARWRnZQ==
|
|
Tests - Performance
Failed to restore: Cache service responded with 400
|
|
Tests - inventree-python
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-node@1a4442cacd436585916779262731d5b162bc6ec7, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - inventree-python
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0o2guagAAAACuer0gDGf9RITRdF4joYZ7REIzRURHRTMxMTIARWRnZQ==
|
|
Tests - inventree-python
Failed to restore: Cache service responded with 400
|
|
Tests - DB [MySQL]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - DB [MySQL]
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oGkuagAAAAClnVNnV8eFTbS6NKTVTJ7YQ0hJMzBFREdFMDQwNwBFZGdl
|
|
Tests - DB [MySQL]
Failed to restore: Cache service responded with 400
|
|
Tests - DB [PostgreSQL]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - DB [PostgreSQL]
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>012kuagAAAAALw2atngA/TpRV3TpyaPYcUEhMMzBFREdFMDQxMwBFZGdl
|
|
Tests - DB [PostgreSQL]
Failed to restore: Cache service responded with 400
|
|
Tests - DB [SQLite] + Coverage 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - DB [SQLite] + Coverage 3.14
No files were found with the provided path: .coverage. No artifacts will be uploaded.
|
|
Tests - DB [SQLite] + Coverage 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - DB [SQLite] + Coverage 3.11
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0imsuagAAAABINYzRTRWwRL2dqwHKCy4BUEhMMzBFREdFMDQxOABFZGdl
|
|
Tests - DB [SQLite] + Coverage 3.11
No files were found with the provided path: .coverage. No artifacts will be uploaded.
|
|
Tests - DB [SQLite] + Coverage 3.11
Failed to restore: Cache service responded with 400
|
|
Tests - Migrations [PostgreSQL]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests - Migrations [PostgreSQL]
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0s3EuagAAAAAhFpywHzGYRJK/NFEqJxFPUEhMMzBFREdFMDIwNgBFZGdl
|
|
Tests - Migrations [PostgreSQL]
Failed to restore: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
inventree_filters.yml
|
5.15 KB |
sha256:f5c33d09dc6ed77cae7c0e3739aba18a2da9b7d13a74e061058f74e81c41ed55
|
|
|
inventree_settings.json
|
11 KB |
sha256:7a30ce2891145672f440326495069e4fd47f1ad1e7e8f365bea6de05ffdbaab7
|
|
|
inventree_tags.yml
|
14.2 KB |
sha256:3f33e53ad00b6d13ae22b6dc5a8b3db62f2778b2907ec5eba7b0b4be5a8d89a6
|
|
|
schema.yml
|
96.6 KB |
sha256:0f11f0a1442df74a659bd75d28833337176e840143da4222bdee35f68faa7529
|
|