Question/Bug regarding versioning on openupm compared to github about openupm HOT 2 CLOSED

Thanks for the very detailed explanation! I will fix the issue.

Regarding the upm split branch thing, this was a suggestion from the medium article linked from your documentation. I also noticed that a lot of the content in that article was very outdated. Would be nice with a new tutorial on this for future users!

Anyway, thanks! Have a great day :)

from openupm.

Because of the package.json version of tag upm/1.0.0 is 0.0.1: https://github.com/appylar/published-unity-sdk/blob/b942b0100ba0c6fa500c8f91738cf0d4b974fc0a/package.json

This will be treated as a failure by build-pipeline in the future (refs #4483). But for now, we let it pass and published 0.0.1.

You can bump the version to 1.0.1, then create Git tag 1.0.1 to fix this.

I checked your ci.yml (https://github.com/appylar/published-unity-sdk/blob/main/.github/workflows/ci.yml), you're using semantic-release-action, it uses git tags to detect the initial version. That may cause the first released version mismatch. Try to generate a new commit to trigger another build, then verify the package.json version with the Git tag. It could be an empty commit like:

git commit --allow-empty -m "fix: rebuild package.json version"
git push

BTW, the split upm branch is no longer needed by our build-pipeline which supports detecting the package.json path automatically.

from openupm.