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
It can be easilly seen that current versions in the beginning This is breaking among other things also documentation where on the read the docs where the latest stable version is still 4.5.0... (due this version is last tag):
@auvipy please when releasing keep naming convention of tag name beginning with "v".
The text was updated successfully, but these errors were encountered:
After latest release with tag beginning with "v" documentation is better but still partially broken:
stable is pointing to latest stable version but still there is message pointing to 4.5:
latest is still pointing to 4.5 release:
Not sure why this is happening and how this can be fixed. From readthedocs documentation:
In the normal case, the latest version will always point to the most up to date development code. If you develop on a branch that is different than the default for your VCS, you should set the Default Branch to that branch.
You should push a tag for each version of your project. These tags should be numbered in a way that is consistent with semantic versioning. This will map to your stable branch by default.
Since version of kombu 4.5.0 the tag naming convention is changed which broke ordering of releases:
It can be easilly seen that current versions in the beginning This is breaking among other things also documentation where on the read the docs where the latest stable version is still 4.5.0... (due this version is last tag):
@auvipy please when releasing keep naming convention of tag name beginning with "v".
The text was updated successfully, but these errors were encountered: