Skip to content

Invalid package version for non-tagged packages

Follow Up

This is a follow up of #120 (closed), respectively #120 (comment 28883).

Bug

See the issue #120 (closed).

  • The version in the pipeline should be the same as the local, but it isn't (1.17.5.dev54+gc6c9c48.d20220301 vs 0.1.dev50+g0ba106e)
  • I suppose this isn't the fault of Python / the Python SCM module
  • Instead I suppose the tags are not "visible" because they're not fetched (or alike) when the pipeline runes

It's not very critical, since these versions are only used for the package in…

  • all review environments
  • the testing environment

However, it is a bit messy because all non-tagged packages are uploaded with version 0.1.dev… instead of the real dev version.

Pipeline Examples

It is a bit weird, because in Translucent's pipelines it doesn't work.
However, in other pipelines it works:

I am not sure if these are some side effects right here, or if there are different Git(Lab) repository settings here.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information