Version control

Hi @popcron,

Thanks for making this awesome UPM package. I’m the creator of the OpenUPM platform, an open-source UPM registry, and continuous build service based on Git tags. It’s hosting more than 200+ open-source UPM packages at the time of writing.

To make it happen, I would suggest you make GitHub releases (which create Git tags) for version control. It can be achieved either manually or using an automatic approach.

In your case, the new release would be 1.6.6 or v1.6.6. After your GitHub release, our build pipelines will detect the changes and build UPM packages in 5-10 minutes. Then you can visit your package at https://openupm.com/packages/com.popcron.gizmos/.

Hopeful this makes sense for you.

[popcron]

Yeah that’s all fine

[favoyang]

Hi @popcron,

Thanks for the link. I’ve noticed they’ve added the support to auth, and a hacky way to work with GitHub registry. Both make sense for privacy registries.

For other parts, I shared a similar feeling. The reasons I create OpenUPM are

• It seems the Unity asset store is working well. It has many thousands of asset here, and will eventually support UPM format as the first citizen for both free and paid assets. There’s no reason to stop using it.
• I want to fill the missing piece of the puzzle to the Unity eco-system, which is supporting and growing open-source projects in an open way. The process should be as low-friction as possible. By simply creating a Git tag and perhaps using a CI to automate.

I can not stop other forks to submit your packages, it basically how the system works, so I will leave it as now. The package has a pending state which will alert users it’s not available yet. And they can always navigate to your website to install it via Git URL.