Viash 0.9.0-RC5
Pre-releaseViash 0.9.0-RC5 (2024-06-13): Improvements for CI
Dependencies now use vsh
as the default organization level. This means that the organization level is now optional in the repo
field of the dependencies.
Improved how the docker image name is generated to be more predictable.
MINOR CHANGES
-
resources_test
: This field is removed again from the_viash.yaml
as it was decided to impliment this temporary functionality using theinfo
field (PR #711). -
docker_engine
: Deprecateregistry
,organization
andtag
fields in thedocker_engine
(PR #712). Currently these are hardly ever used and instead theimage
field is used to specify the full image name. -
docker_engine
: Addtarget_package
field to thedocker_engine
(PR #712). This field, together with thetarget_organization
is used to specify the full built container image name. The fields use proper fallback for the values set in the component config and package config. -
organization
: Remove theorganization
field from the component config (PR #712). The value is now directly used by thedocker_engine
as a fallback from thetarget_organization
field.
BUG FIXES
-
build_info
: Correctly set the.build_info.executable
tomain.nf
when building a component with a Nextflow runner (PR #720). -
vsh organization
: ViashHub repositories now usevsh
as the default organization (PR #718).
Instead of having to specifyrepo: vsh/repo_name
, you can now just specifyrepo: repo_name
, which is now also the prefered way. -
testbenches
: Add a testbench to verify dependencies in dependencies from scratch (PR #721).
The components are built from scratch and the dependencies are resolved from the local repositories.