Bug 1891564

Latest upstream release: 1.7.1
Current version/release in rawhide: 1.6.1-1.fc33
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/29768/

Latest upstream release: 1.7.2
Current version/release in rawhide: 1.6.1-1.fc33
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/29768/

I need this to build ansible-base docs. In the current version there's a bug with python 3.9 that breaks things, and it's fixed in this new version. 

I'm going to just avoid the docs for now, but it would be nice to fix this sometime.

Latest upstream release: 1.7.3
Current version/release in rawhide: 1.6.1-1.fc33
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/29768/

Latest upstream release: 1.8
Current version/release in rawhide: 1.7.3-1.fc35
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/29768/

Latest upstream release: 1.8.1
Current version/release in rawhide: 1.7.3-1.fc35
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/29768/

Latest upstream release: 1.8.2
Current version/release in rawhide: 1.7.3-1.fc35
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/29768/

Python packages have started to require version 1.8.x, so it'll be good to update this package if possible.

Cheers

Latest upstream release: 1.9.0a1
Current version/release in rawhide: 1.7.4-3.fc35
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/29768/

1.8.2 does not build and 1.9.0a1 still has bugs

https://github.com/samuelcolvin/pydantic/issues/3562

Latest upstream release: 1.9.0a2
Current version/release in rawhide: 1.7.4-3.fc35
URL: https://github.com/samuelcolvin/pydantic

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/29768/

Version 1.9.0 is available since 2021-12-31. It contains a bug fix for https://github.com/samuelcolvin/pydantic/issues/3300, which is needed to update python-fastapi.

Please consider updating this in time for Fedora 36! Thanks.

That was fast! Thanks.

Yeah the problem is that the version monitoring is picking up the alpha version as the latest one...

(In reply to Susi Lehtola from comment #14)
> Yeah the problem is that the version monitoring is picking up the alpha
> version as the latest one...

I just updated https://release-monitoring.org/project/29768/ by adding “a;b;rc” to the “Pre-release filter”, which will properly mark pre-releases in the web UI, and in “Version filter”, which doesn’t produce any visible difference in the web UI but will keep URM from filing RHBZ bugs for pre-releases. Hopefully that’s helpful.

(In reply to Ben Beasley from comment #15)
> (In reply to Susi Lehtola from comment #14)
> > Yeah the problem is that the version monitoring is picking up the alpha
> > version as the latest one...
> 
> I just updated https://release-monitoring.org/project/29768/ by adding
> “a;b;rc” to the “Pre-release filter”, which will properly mark pre-releases
> in the web UI, and in “Version filter”, which doesn’t produce any visible
> difference in the web UI but will keep URM from filing RHBZ bugs for
> pre-releases. Hopefully that’s helpful.

Nope, it still shows

All versions: 
1.9.0a2, 1.9.0a1, 1.9.0, 1.8.2, 1.8.1, 1.8, 1.7.4, 1.7.3, 1.7.2, 1.7.1, 1.7, 1.6.2, 1.6.1, 1.6, 1.5.1, 1.5, 1.4, 1.3, 1.2, 1.1.1, 1.1, 1.0b2, 1.0b1, 1.0, 0.32.2, 0.32.1, 0.32, 0.31.1, 0.31, 0.30.1, 0.30, 0.29, 0.28, 0.27a1, 0.27, 0.26, 0.25, 0.24, 0.23, 0.22, 0.21, 0.20.1, 0.20a1, 0.20, 0.19, 0.18.2, 0.18.1, 0.18, 0.16.1, 0.16, 0.15, 0.14, 0.13.1, 0.13, 0.12.1, 0.12, 0.11.2, 0.11.1, 0.11, 0.10, 0.9.1, 0.9, 0.8, 0.7.1, 0.7, 0.6.4, 0.6.3, 0.6.2, 0.6.1, 0.6, 0.5, V0.17
Latest version: 1.9.0a2

Changing the versioning to "semantic" helped.

(In reply to Susi Lehtola from comment #16)
> (In reply to Ben Beasley from comment #15)
> > (In reply to Susi Lehtola from comment #14)
> > > Yeah the problem is that the version monitoring is picking up the alpha
> > > version as the latest one...
> > 
> > I just updated https://release-monitoring.org/project/29768/ by adding
> > “a;b;rc” to the “Pre-release filter”, which will properly mark pre-releases
> > in the web UI, and in “Version filter”, which doesn’t produce any visible
> > difference in the web UI but will keep URM from filing RHBZ bugs for
> > pre-releases. Hopefully that’s helpful.
> 
> Nope, it still shows
> 
> All versions: 
> 1.9.0a2, 1.9.0a1, 1.9.0, 1.8.2, 1.8.1, 1.8, 1.7.4, 1.7.3, 1.7.2, 1.7.1, 1.7,
> 1.6.2, 1.6.1, 1.6, 1.5.1, 1.5, 1.4, 1.3, 1.2, 1.1.1, 1.1, 1.0b2, 1.0b1, 1.0,
> 0.32.2, 0.32.1, 0.32, 0.31.1, 0.31, 0.30.1, 0.30, 0.29, 0.28, 0.27a1, 0.27,
> 0.26, 0.25, 0.24, 0.23, 0.22, 0.21, 0.20.1, 0.20a1, 0.20, 0.19, 0.18.2,
> 0.18.1, 0.18, 0.16.1, 0.16, 0.15, 0.14, 0.13.1, 0.13, 0.12.1, 0.12, 0.11.2,
> 0.11.1, 0.11, 0.10, 0.9.1, 0.9, 0.8, 0.7.1, 0.7, 0.6.4, 0.6.3, 0.6.2, 0.6.1,
> 0.6, 0.5, V0.17
> Latest version: 1.9.0a2

It *really* makes no difference in the web UI. It doesn’t change the result of a “test” version check, and it doesn’t remove any existing versions from the list. It does still affect which versions you get bugs for, even though there’s absolutely no way to verify that other than “wait and see.” The feature could definitely use some improvement.

Interesting, since changing to semantic changed the output so that the alpha and beta releases went away.

(In reply to Susi Lehtola from comment #19)
> Interesting, since changing to semantic changed the output so that the alpha
> and beta releases went away.

They’re sorted at the very end now, since SemVer expects something like 1.9.0-a1. It does fix the 1.9.0 alpha versions sorting newer, but at the cost of the version order being totally wacky.