v4.4.33

Release notes

Changes

• Fixed that generate_certificate_for_development_purposes_for_product generated a new TLS-certificate for development-purposes on every single run instead of keeping the existing one until it expires. The certificate-files are named after the product (<productname>DevelopmentCertificate.crt), but the check whether a certificate already exists looked for a file named after the domain (<productname>.test.local.crt), which is never written - so the check never found anything and every build of a repository which generates such a certificate replaced it. The check now uses the name under which the certificate is really written; the generated files keep their names, so nothing which refers to them (for example a Dockerfile which embeds the certificate) is affected
• Fixed that translating the xlf-files of a project stopped at the first language which the configured LibreTranslate-instance does not offer. Such an instance knows a limited set of languages while a project states the languages it wants, so a project which has one of the others ended the whole run with the error of that language - and every language behind it stayed untranslated as well, including the ones the instance knows. The languages the instance offers are asked of it now (get_supported_translation_languages), the others are skipped and reported by name, and their texts stay in the base-language, which is what the fallback of every translation-mechanism exists for
• Fixed that the testcases for the resolution of environment-variables and of the OCI-registry-credentials failed in a containerized build (scbuildcodeunits -c) although they passed in a build on the host. These testcases replaced the configuration-folder of the current user by a temporary one to become independent of the machine they run on, but the machine-wide configuration has a second source which has precedence over that folder: the configuration-file which a host mounts into a build-container. In a containerized build that mount exists, so the testcases read the real credentials of the build-machine instead of the ones they had arranged. The testcases now isolate both sources, so their result no longer depends on whether they run on a developer-machine or inside a build-container. Only the testcases are affected; the behavior of the product is unchanged