Adding ferpa #4273
gearnodemake.yaml
on: pull_request
build
2m 5s
release-snapshot
5m 49s
test-e2e
4m 41s
Annotations
14 warnings
|
test-e2e
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, docker/setup-compose-action@364cc21a5de5b1ee4a7f5f9d3fa374ce0ccde746, docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130. 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/
|
|
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. 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/
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. 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/
|
|
lint
The `useMutation` hook should be used with an explicit generated Typescript type, e.g.: useMutation<AuditGraphUpdateMutation>(...)
|
|
lint
The `useMutation` hook should be used with an explicit generated Typescript type, e.g.: useMutation<AuditGraphCreateMutation>(...)
|
|
lint
The `useMutation` hook should be used with an explicit generated Typescript type, e.g.: useMutation<AssetGraphCreateMutation>(...)
|
|
lint
The `useMutation` hook should be used with an explicit generated Typescript type, e.g.: useMutation<AssetGraphDeleteMutation>(...)
|
|
lint:
apps/console/src/components/tasks/TasksCard.tsx#L174
The `useMutation` hook should be used with an explicit generated Typescript type, e.g.: useMutation<null>(...)
|
|
lint:
apps/console/src/components/tasks/TasksCard.tsx#L165
The `useMutation` hook should be used with an explicit generated Typescript type, e.g.: useMutation<TasksCardDeleteMutation>(...)
|
|
lint
The `usePaginationFragment` hook should be used with an explicit generated Typescript type, e.g.: usePaginationFragment<LinkedObligationsDialogQuery_fragment>(...)
|
|
lint:
apps/console/src/components/documents/LinkedDocumentsDialog.tsx#L99
The `usePaginationFragment` hook should be used with an explicit generated Typescript type, e.g.: usePaginationFragment<LinkedDocumentsDialogQuery_fragment>(...)
|
|
lint:
apps/console/src/components/controls/LinkedControlsDialog.tsx#L128
The `usePaginationFragment` hook should be used with an explicit generated Typescript type, e.g.: usePaginationFragment<LinkedControlsDialogControlsQuery>(...)
|
|
lint
The `usePaginationFragment` hook should be used with an explicit generated Typescript type, e.g.: usePaginationFragment<LinkedAuditsDialogQuery_fragment>(...)
|
|
release-snapshot
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, anchore/sbom-action/download-syft@deef08a0db64bfad603422135db61477b16cef56, anchore/sbom-action@deef08a0db64bfad603422135db61477b16cef56, anchore/scan-action@8d2fce09422cd6037e577f4130e9b925e9a37175, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130, goreleaser/goreleaser-action@e435ccd777264be153ace6237001ef4d979d3a7a. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-artifacts
Expired
|
46.6 MB |
sha256:28ab04fc61665e966af6355bcdae871d8bd9618d346a18e61d9b85fd9353a783
|
|
|
coverage-reports
|
1.29 MB |
sha256:37e68279add4069ac9b7801abbbccb7c018e324b3863cd9ca555cd6cc2600e0b
|
|
|
junit-e2e-results
|
8.3 KB |
sha256:abfb0c4cf9453824644792d361bc216009ee57cbb3e9740e00d4aa1c7309adaf
|
|
|
junit-results
|
7.72 KB |
sha256:b2a5cd8fa773e27ef9faa397e329db122a6ff9af92c1fcfb27d744ed2345436e
|
|
|
probo-release-snapshot-2.cyclonedx.json
|
121 KB |
sha256:2118de2d1ecd956703d4cf17852ac2f1debd428d0091246de32fcd75a38c574e
|
|