You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version needs to be increased every time you modify an existing package.
Otherwise, the higest old version will be installed and tested in our CI and the change in the package won't have effect. The linter should complain about this.
This has been an issue recently in several PR that were using the date as version in the format day.month.year or month.day.year instead of using the tool version. We should use the tool version and not the date. If there is no tool version, the version should be 0.0.0.YYYYMMDD, using the 4th segment for the date. For example:
One problem to enforce this in the linter is that it will fail if we decrease the version because it is wrong. We have done this a few times by deleting the current packages in myget. Example: #890 (review)
As mentioned in our documentation:
Otherwise, the higest old version will be installed and tested in our CI and the change in the package won't have effect. The linter should complain about this.
This has been an issue recently in several PR that were using the date as version in the format
day.month.year
ormonth.day.year
instead of using the tool version. We should use the tool version and not the date. If there is no tool version, the version should be0.0.0.YYYYMMDD
, using the 4th segment for the date. For example:The linter should check that the version follows the correct format (this is done already) and also that the version has been increased.
All this is already documented in our wiki, but if someone feels it needs more detail, please improve the Wiki as well. 😄
The text was updated successfully, but these errors were encountered: