chore: introduce import order #8705
BuildJobs.yml
on: pull_request
Check SHA in GH Actions
8s
Matrix: build
Matrix: Run automated end-to-end tests
Publish E2E test summary
35s
Annotations
13 errors and 61 warnings
|
Run automated end-to-end tests (2)
Process completed with exit code 1.
|
|
Run automated end-to-end tests (2)
@mendix/datagrid-date-filter-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-date-filter-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)
|
|
Run automated end-to-end tests (4)
Process completed with exit code 1.
|
|
Run automated end-to-end tests (4)
@mendix/rich-text-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/rich-text-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)
|
|
Failed Test: compares with a screenshot for rich text inside modal popup layout:
packages/pluggableWidgets/rich-text-web/e2e/RichText.spec.js#L0
compares with a screenshot for rich text inside modal popup layout: Error: expect(locator).toHaveScreenshot(expected) failed
Locator: locator('.mx-name-customWidget1').first()
Expected an image 580px by 536px, received 580px by 490px. 1953 pixels (ratio 0.01 of all image pixels) are different.
Snapshot: richTextModal.png
Call log:
- Expect "toHaveScreenshot(richTextModal.png)" with timeout 5000ms
- verifying given screenshot expectation
- waiting for locator('.mx-name-customWidget1').first()
- locator resolved to <div class="mx-name-customWidget1 form-group no-columns">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- Expected an image 580px by 536px, received 580px by 490px. 6736 pixels (ratio 0.03 of all image pixels) are different.
- waiting 100ms before taking screenshot
- waiting for locator('.mx-name-customWidget1').first()
- locator resolved to <div class="mx-name-customWidget1 form-group no-columns">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- 5370 pixels (ratio 0.02 of all image pixels) are different.
- waiting 250ms before taking screenshot
- waiting for locator('.mx-name-customWidget1').first()
- locator resolved to <div class="mx-name-customWidget1 form-group no-columns">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- captured a stable screenshot
- Expected an image 580px by 536px, received 580px by 490px. 1953 pixels (ratio 0.01 of all image pixels) are different.
- Error: expect(locator).toHaveScreenshot(expected) failed
Locator: locator('.mx-name-customWidget1').first()
Expected an image 580px by 536px, received 580px by 490px. 1953 pixels (ratio 0.01 of all image pixels) are different.
Snapshot: richTextModal.png
Call log:
- Expect "toHaveScreenshot(richTextModal.png)" with timeout 5000ms
- verifying given screenshot expectation
- waiting for locator('.mx-name-customWidget1').first()
- locator resolved to <div class="mx-name-customWidget1 form-group no-columns">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- Expected an image 580px by 536px, received 580px by 490px. 6736 pixels (ratio 0.03 of all image pixels) are different.
- waiting 100ms before taking screenshot
- waiting for locator('.mx-name-customWidget1').first()
- locator resolved to <div class="mx-name-customWidget1 form-group no-columns">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- 5370 pixels (ratio 0.02 of all image pixels) are different.
- waiting 250ms before taking screenshot
- waiting for locator('.mx-name-customWidget1').first()
- locator resolved to <div class="mx-name-customWidget1 form-group no-columns">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- captured a stable screenshot
- Expected an image 580px by 536px, received 580px by 490px. 1953 pixels (ratio 0.01 of all image pixels) are different.
at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/rich-text-web/e2e/RichText.spec.js:141:70
|
|
Failed Test: compares with a screenshot baseline and checks if all datagrid and filter elements are rendered as expected:
packages/pluggableWidgets/datagrid-date-filter-web/e2e/DataGridDateFilter.spec.js#L0
compares with a screenshot baseline and checks if all datagrid and filter elements are rendered as expected: Error: expect(locator).toHaveScreenshot(expected) failed
Locator: locator('.mx-name-datagrid1')
6 pixels (ratio 0.01 of all image pixels) are different.
Snapshot: dataGridDateFilter.png
Call log:
- Expect "toHaveScreenshot(dataGridDateFilter.png)" with timeout 5000ms
- verifying given screenshot expectation
- waiting for locator('.mx-name-datagrid1')
- locator resolved to <div class="mx-name-datagrid1 spacing-inner-large widget-datagrid">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- 6 pixels (ratio 0.01 of all image pixels) are different.
- waiting 100ms before taking screenshot
- waiting for locator('.mx-name-datagrid1')
- locator resolved to <div class="mx-name-datagrid1 spacing-inner-large widget-datagrid">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- captured a stable screenshot
- 6 pixels (ratio 0.01 of all image pixels) are different.
- Error: expect(locator).toHaveScreenshot(expected) failed
Locator: locator('.mx-name-datagrid1')
6 pixels (ratio 0.01 of all image pixels) are different.
Snapshot: dataGridDateFilter.png
Call log:
- Expect "toHaveScreenshot(dataGridDateFilter.png)" with timeout 5000ms
- verifying given screenshot expectation
- waiting for locator('.mx-name-datagrid1')
- locator resolved to <div class="mx-name-datagrid1 spacing-inner-large widget-datagrid">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- 6 pixels (ratio 0.01 of all image pixels) are different.
- waiting 100ms before taking screenshot
- waiting for locator('.mx-name-datagrid1')
- locator resolved to <div class="mx-name-datagrid1 spacing-inner-large widget-datagrid">…</div>
- taking element screenshot
- disabled all CSS animations
- waiting for fonts to load...
- fonts loaded
- attempting scroll into view action
- waiting for element to be stable
- captured a stable screenshot
- 6 pixels (ratio 0.01 of all image pixels) are different.
at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-date-filter-web/e2e/DataGridDateFilter.spec.js:21:36
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Run release task on windows-latest
The operation was canceled.
|
|
Plan E2E matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run automated end-to-end tests (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Publish E2E test summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run code quality check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run code quality check:
automation/utils/src/changelog-parser/index.ts#L17
`path` import should occur before import of `../version`
|
|
Run code quality check:
automation/utils/src/changelog-parser/index.ts#L4
`./parser/module/module` import should occur before import of `./parser/widget/widget`
|
|
Run code quality check:
automation/utils/src/bump-version.ts#L39
'e' is defined but never used. Allowed unused caught errors must match /^_/u
|
|
Run code quality check:
automation/utils/src/bump-version.ts#L3
`enquirer` import should occur after import of `process`
|
|
Run code quality check:
automation/utils/src/bump-version.ts#L1
`chalk` import should occur after import of `process`
|
|
Run code quality check:
automation/utils/src/build-config.ts#L51
An interface declaring no members is equivalent to its supertype
|
|
Run code quality check:
automation/utils/src/build-config.ts#L34
An interface declaring no members is equivalent to its supertype
|
|
Run code quality check:
automation/utils/src/build-config.ts#L32
An interface declaring no members is equivalent to its supertype
|
|
Run code quality check:
automation/utils/src/api/contributor.ts#L5
`chalk` import should occur before import of `../fetch`
|
|
Run code quality check:
automation/utils/src/api/contributor.ts#L3
`zod` import should occur before import of `../fetch`
|
|
Run release task on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on ubuntu-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on ubuntu-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on ubuntu-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on ubuntu-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L3
`react` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/utils.ts#L2
`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.tsx#L3
`./utils` import should occur before import of `../typings/TXhHdGFnProps`
|
|
Run release task on windows-latest:
packages/pluggableWidgets/google-tag-web/src/TXhHdGFn.editorConfig.ts#L2
`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
ctrf-reports-0
|
5.25 KB |
sha256:d75cb8df8306c41330ec0b25e5bc3665011ae3a82c392c3d5742c70e46656cb0
|
|
|
ctrf-reports-1
|
3.91 KB |
sha256:facc29838c31f83ca2a2b25a02d7c56c25d16a2d15b21d17c3fa2c5be265205b
|
|
|
ctrf-reports-2
|
5.04 KB |
sha256:ee6088dc37f343a5f7c00e922569280f6312bd405664fdd13c6e83de43b1423e
|
|
|
ctrf-reports-3
|
3.43 KB |
sha256:c0f6c093b461f09f2354fa9f3e87706c0567927feec7efb3ff977e6cb97299c2
|
|
|
ctrf-reports-4
|
5.37 KB |
sha256:dfbf722a2a0a80a20aa58d00ecb643960ee7c114be399cac01a8c2ac9b15bda7
|
|
|
ctrf-reports-5
|
5.85 KB |
sha256:e5cdabbc240d855412abf5a97eed4e56e2a5c618dc4e2aae05be25489d5a216f
|
|
|
ctrf-reports-6
|
3.61 KB |
sha256:30f83f92adb404786b56c161114339d2e09d832cd318696d0cd40a0d78c2d534
|
|
|
ctrf-reports-7
|
5.34 KB |
sha256:51bf971601fad1a7c8ccc5adf20944bb107cceb9ea5a85a984ca7a11fce6c4d5
|
|
|
test-screenshot-results-2
|
2.98 MB |
sha256:abbf778fe6c52797b45605b01664ebc65b92644dd3210d6d9b2f6ae0830e7036
|
|
|
test-screenshot-results-4
|
946 KB |
sha256:d278f04358b40ae75b6b9efcb79cadb94bf1c64ab0e822481481e60410b734b6
|
|