Git tags naming issue on OpenUPM about toolnity

[DTeruel]

The second option is what I did for now. :) Thanks for your help! El dom., 9 oct. 2022 5:44, Favo Yang ***@***.***> escribió:

…

We don't have a flag for an "archived" repository yet. It's something good to have for an archived GitHub repository or a manual flag for one sub-package of monorepo like this. For now, you can consider a workaround - Remove the openupm package meta file (YAML), which will keep your packages on the registry, but only the web page is removed. - Or, change the gitTagPrefix to something like non-existed-prefix, to stop the pipeline from tracking for new versions. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIGLCGA3Q6AO7UTHEW7ON73WCI5QVANCNFSM6AAAAAARAKYJHI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[DTeruel]

Hey! The good one should be 'toolnity/2.0.0'. the other ones were tests until I understood how it works with the subpackages.

But anyway, I'm not sure if it will work since this is not a package anymore. Is a Unity project with different subpackages inside, and this project is used to test all the packages and have the "main index" in there.
Thanks!

[favoyang]

Hey! The good one should be 'toolnity/2.0.0'. the other ones were tests until I understood how it works with the subpackages.

You need to choose one of the git tag naming pattern mentioned above to achieve this (help our pipelines to detect the correct git tag)

If the "index" package is no longer needed, please consider removing from the openupm.

[DTeruel]

It's not a package anymore but I'd like to keep the oldest versions for compatibility woth older projects. The only thing I want know it's to avoid new builds (or waiting for an specific tag as 'toolnity'). It's that possible? El sáb., 8 oct. 2022 20:19, Favo Yang ***@***.***> escribió:

…

Hey! The good one should be 'toolnity/2.0.0'. the other ones were tests until I understood how it works with the subpackages. You need to choose one of the git tag naming pattern mentioned above to achieve this (help our pipelines to detect the correct git tag) If the "index" package is no longer needed, please consider removing from the openupm. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIGLCGHF2FCX3H5A7VMZIGLWCG3KPANCNFSM6AAAAAARAKYJHI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[favoyang]

We don't have a flag for an "archived" repository yet. It's something good to have for an archived GitHub repository or a manual flag for one sub-package of monorepo like this.

For now, you can consider a workaround

• Remove the openupm package meta file (YAML), which will keep your packages on the registry, but only the web page is removed.
• Or, change the gitTagPrefix to something like non-existed-prefix, to stop the pipeline from tracking for new versions.