Closed georgehwho closed 1 year ago
Hello George,
CircleCI's orbs do not have full semver support. A CircleCI orb can only be published as a numbered version X.Y.Z
, or with a dev
tag, such as namespace/orb-name@dev:x
. Orbs can also be called via @volatile
for the last published release (does not respect version numbers). So unfortunately it is not a limitation of this orb or tool, it is the design of the orbs product.
More information can be found here: https://circleci.com/docs/orb-concepts#semantic-versioning
If you are attempting to publish an alpha version of an orb, I recommend using a dev
tag. This however is not supported by the automatic deployment job currently, due to the default tag regex.
Orb version:
11.1
What happened:
I tried to deploy a private orb with the tag
v0.0.0-alpha-1
and received the following error in the Publishing Orb Release stepExpected behavior:
Per Semver's spec: https://semver.org/
The example shows 1.0.0-alpha.1, but 0.0.0-alpha-1 also meets that requirement so I expected my tag to work.
Additional Information:
Looks like the function
validateProdTag
here is restricting the tag: https://github.com/CircleCI-Public/orb-tools-orb/blob/master/src/scripts/publish.sh#L2