Nice3point / RevitToolkit

Toolkit for Revit plugin development
MIT License
81 stars 12 forks source link

Version 2025.0.3 is not open source? #12

Closed ricaun closed 1 month ago

ricaun commented 1 month ago

I was planning to do a PR and noticed the version difference from the nuget and this repository.

I wonder the reason of that, and what changed between version 2025.0.2 and 2025.0.3.

image

image

Nice3point commented 1 month ago

изображение

2025.0.3 Minor fix related to removal of unused dependency. The develop branch is usually up to date always

The release will be published in the main branch in a few minutes, sorry for its unavailability

ricaun commented 1 month ago

I didn't noticed in develop branch, there is no github action for that branch.

You push the package from your machine, I thought you use the github action to push at the same time with the release in github.

At least is how I do it, I can only push a package in nuget/github using github action and release a version.

Nice3point commented 1 month ago

I didn't do automatic publishing on Nuget because of high risks of invalid versions or accidental pushes to the main branch. And not wanting to frequently update token in Github secrets for all Open source projects. Nuget package cannot be removed, only hidden, so it is much more convenient and reliable to build and remove outdated versions locally. If the project becomes more global, I will reconsider this behavior

ricaun commented 1 month ago

I didn't do automatic publishing on Nuget because of high risks of invalid versions or accidental pushes to the main branch. And not wanting to frequently update token in Github secrets for all Open source projects. Nuget package cannot be removed, only hidden, so it is much more convenient and reliable to build and remove outdated versions locally. If the project becomes more global, I will reconsider this behavior

I found out recently you can remove from the Nuget, but you cannot replace the version if you remove. Go in the Contact Support in your package and there is a option for that.

In my case I can only update the main branch by creating a PR and approving, after the Github action build everything with tests in some cases.