Skip to content

deps:chore - update dependency node-releases to v2.0.17 #2940

deps:chore - update dependency node-releases to v2.0.17

deps:chore - update dependency node-releases to v2.0.17 #2940

Triggered via pull request December 1, 2023 19:31
Status Failure
Total duration 53s
Artifacts

messages-pipeline.yml

on: pull_request
lint-coverage-build-security
40s
lint-coverage-build-security
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
lint-coverage-build-security
import 'github.com/ZupIT/horusec-platform/messages/config/providers' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/go-chi/cors' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-devkit/pkg/entities/email' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-devkit/pkg/enums/email' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-platform/messages/internal/enums/templates' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-platform/messages/internal/services/mailer' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-devkit/pkg/entities/email' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-devkit/pkg/enums/queues' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-devkit/pkg/services/broker' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
import 'github.com/ZupIT/horusec-devkit/pkg/services/broker/packet' is not allowed from list 'Main' (depguard)
lint-coverage-build-security
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/