Release notes

Changes

Fixed that scupdatelockfiles (update_lock_files_of_dotnet_codeunit) did not update the lock-files of a dotnet-codeunit in many cases: the restore is called with --force and --force-evaluate now. Without --force a restore whose inputs did not change since the last restore was skipped entirely (no-op restore) and wrote no lock-file at all, for example into an empty or newly created packages.lock.json. Without --force-evaluate an existing lock-file was taken as it is instead of being resolved again
Fixed that a build which runs in a container (scbuildcodeunitsc, scbuildcodeunits -c) ignored the custom registries defined in ~/.ScriptCollection/GlobalCache/OCIImages/ImageRegistries.csv and pulled every image from the rate-limited upstream-registry of .ScriptCollection/OCIImages/ImageDefinition.csv instead. That file of the host is mounted read-only into the build-container now (to /Workspace/ScriptCollectionConfiguration/OCIImages/ImageRegistries.csv); no other part of the configuration-folder is exposed to the container
The warning which the documentation announces when an image is taken from its fallback-registry is actually logged now (once per image), so a missing entry in ImageRegistries.csv is visible in the build-log

No results found