The biggest impact on this repository is that the version of the conan package is now determined by the version key in conandata.yml and no longer determined based on the git tag. During a push the Conan user, channel is determined based Github runner context, see the conan-recipe-versions.yml in the Cura-workflows and the semver build metadata is added from the sha of the reference name (git hash).
Furthermore the Uranium dependencies maintained by UltiMaker (e.q.: pyarcus) are no longer specified in the conanfile.py but are also present in the conandata.yml which allows us to automate the user and channel on main and release branches in the future. Since it is a yaml file which can be read in and easily changed by an automated workflow. For instance change the Conan channel to stable when we create the release branch. Or pin to specific conan package release version (e.q.: curaengine_grpc_definitions/0.2.0@_/_) when we create an actual release.
When you now create a release branch now you would need to do this manually.
Type of change
[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
Description
Ported a lot of workflow to use the reusable workflows in the new Cura-workflows repository. See PR: https://github.com/Ultimaker/cura-workflows/pull/1
The biggest impact on this repository is that the version of the conan package is now determined by the
versionkey inconandata.ymland no longer determined based on the git tag. During a push the Conan user, channel is determined based Github runner context, see theconan-recipe-versions.ymlin the Cura-workflows and the semver build metadata is added from the sha of the reference name (git hash).Furthermore the Uranium dependencies maintained by UltiMaker (e.q.: pyarcus) are no longer specified in the
conanfile.pybut are also present in theconandata.ymlwhich allows us to automate the user and channel on main and release branches in the future. Since it is a yaml file which can be read in and easily changed by an automated workflow. For instance change the Conan channel tostablewhen we create the release branch. Or pin to specific conan package release version (e.q.:curaengine_grpc_definitions/0.2.0@_/_) when we create an actual release.Type of change
How Has This Been Tested?
Test Configuration:
Checklist: