mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
12e0c72d5c
We believe the Blakduck logic is currently faulty. We have had a violation on an NPM dependency, and Blackduck keeps reporting it despite our having removed the dependency. We believe that what is happening is that, in the first step of checking, we udpate the Haskell dependencies, _and then check the validity of the whole project_, which includes the NPM deps. Because that fails, we never get to the step where we actually update the NPM deps, and Blackduck is stuck forever. The solution is to not fail on violations for the Haskell update steps. Haskell deps are still checked in the second step, because, again, it is checking the whole project. CHANGELOG_BEGIN CHANGELOG_END |
||
---|---|---|
.. | ||
cron | ||
da-ghc-lib | ||
docker | ||
patch_bazel_windows | ||
bash-lib.yml | ||
BUILD | ||
build-unix.yml | ||
build-windows.yml | ||
build.yml | ||
check-changelog.sh | ||
check-protobuf-against-stable.sh | ||
clean-up.yml | ||
clear-shared-segments-macos.yml | ||
compatibility_ts_libs.yml | ||
compatibility-windows.yml | ||
compatibility.yml | ||
configure-bazel.sh | ||
copy-unix-release-artifacts.sh | ||
copy-windows-release-artifacts.sh | ||
dev-env-install.sh | ||
dev-env-push.py | ||
job-variables.yml | ||
oracle_image | ||
postgresql.conf | ||
prs.yml | ||
publish-artifactory.sh | ||
publish-platform-independence-dar.yml | ||
remap-scala-test-short-names.ps1 | ||
report-end.yml | ||
report-start.yml | ||
slack_user_ids | ||
tell-slack-failed.yml | ||
upload-bazel-metrics.yml | ||
windows-diagnostics.ps1 |