chore(deps-dev): bump flatted from 3.4.1 to 3.4.2 in /application #348
main-ci.yml
on: push
ci
/
...
/
π¦ Prepare configuration
5s
Matrix: ci / continuous-integration-actions
ci
/
...
/
π‘οΈ CodeQL Analysis
1m 9s
ci
/
...
/
π‘οΈ Dependency Review
0s
Generate Documentation
52s
share-new-blog-posts
/
announce
Annotations
18 errors and 9 warnings
|
ci / continuous-integration / ποΈ Build
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration / ποΈ Build
The operation was canceled.
|
|
ci / continuous-integration / π‘οΈ CodeQL Analysis
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration / π‘οΈ CodeQL Analysis
The operation was canceled.
|
|
ci / continuous-integration-actions (.github/actions/generate-brand-content) / π‘οΈ CodeQL Analysis
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration-actions (.github/actions/generate-brand-content) / π‘οΈ CodeQL Analysis
The operation was canceled.
|
|
ci / continuous-integration-actions (.github/actions/validate-manifest) / π‘οΈ CodeQL Analysis
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration-actions (.github/actions/validate-manifest) / π‘οΈ CodeQL Analysis
The operation was canceled.
|
|
ci / continuous-integration-actions (.github/actions/generate-blog-post) / π‘οΈ CodeQL Analysis
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration-actions (.github/actions/generate-blog-post) / π‘οΈ CodeQL Analysis
The operation was canceled.
|
|
ci / continuous-integration / π Lint
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration / π Lint
The operation was canceled.
|
|
Internal - Main - Continuous Integration
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
Internal - Main - Continuous Integration
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
Internal - Main - Continuous Integration
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
Internal - Main - Continuous Integration
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
Internal - Main - Continuous Integration
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
Internal - Main - Continuous Integration
Canceling since a higher priority waiting request for Internal - Main - Continuous Integration-refs/heads/main exists
|
|
ci / continuous-integration-actions (.github/actions/generate-brand-content) / ποΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration-actions (.github/actions/generate-blog-post) / ποΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration-actions (.github/actions/validate-manifest) / ποΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration-actions (.github/actions/generate-brand-content) / π§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration-actions (.github/actions/validate-manifest) / π§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration-actions (.github/actions/generate-blog-post) / π§ͺ Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration / ποΈ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration / π Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ci / continuous-integration / π Lint
No report files found
|