Corex Generators + New Components #103
elixir.yml
on: pull_request
Matrix: e2e-tests
Matrix: installer-tests
Matrix: integration-tests
Matrix: unit-tests
Annotations
21 errors and 11 warnings
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test default app home page GET / returns 200 and body contains Corex (Corex.Integration.CodeGeneration.CorexIntegrationTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test GET / (PhxBlogWeb.PageControllerTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
feature home page has no accessibility violations (PhxBlogWeb.PageControllerA11yTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test connected mount (PhxBlogWeb.ExampleLiveTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test newly generated app has no warnings or errors (Corex.Integration.CodeGeneration.AppWithNoOptionsTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test GET / (MyAppWeb.PageControllerTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
feature home page has no accessibility violations (MyAppWeb.PageControllerA11yTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test connected mount (MyAppWeb.ExampleLiveTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test app with --no-tidewave compiles, format check passes, and tests pass (Corex.Integration.CodeGeneration.CorexIntegrationTest)
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
test development workflow works as expected (Corex.Integration.CodeGeneration.AppWithNoOptionsTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
The strategy configuration was canceled because "integration-tests._1_17_3_27_1_2" failed
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test app with --theme uno:leo compiles, format check passes, and tests pass (Corex.Integration.CodeGeneration.CorexIntegrationTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test development workflow works as expected (Corex.Integration.CodeGeneration.AppWithNoOptionsTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test GET / (MyAppWeb.PageControllerTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
feature home page has no accessibility violations (MyAppWeb.PageControllerA11yTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test connected mount (MyAppWeb.ExampleLiveTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test app with --no-tidewave compiles, format check passes, and tests pass (Corex.Integration.CodeGeneration.CorexIntegrationTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test GET / (PhxBlogWeb.PageControllerTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
feature home page has no accessibility violations (PhxBlogWeb.PageControllerA11yTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test connected mount (PhxBlogWeb.ExampleLiveTest)
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
test newly generated app has no warnings or errors (Corex.Integration.CodeGeneration.AppWithNoOptionsTest)
|
|
Installer tests (OTP 27.3 | Elixir 1.18.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Installer tests (OTP 28.0.1 | Elixir 1.18.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Installer tests (OTP 25.3.2.9 | Elixir 1.15.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Unit tests (OTP 28.0.1 | Elixir 1.18.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Unit tests (OTP 27.3 | Elixir 1.18.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Unit tests (OTP 25.3.2.9 | Elixir 1.15.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
E2E tests (OTP 27.3 | Elixir 1.18.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
E2E tests (OTP 25.3.2.9 | Elixir 1.15.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
E2E tests (OTP 28.0.1 | Elixir 1.18.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Integration tests (OTP 27.1.2 | Elixir 1.17.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|
|
Integration tests (OTP 25.3.2.9 | Elixir 1.15.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@3580539ceec3dc05b0ed51e9e10b08eb7a7c2bb4. 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/
|