Build job failing due to version mismatch

[bryevdv]

Now seeing this on all jobs:

Version mismatch: given version (3.5.dev1+36.gc297d210) != package version (3.5.0.dev1+36.gc297d210)

In the last successful build the dist filename had the .0

++++ ls dist/bokeh-3.5.0.dev1+27.g0aeab18d.tar.gz
+++ basename dist/bokeh-3.5.0.dev1+27.g0aeab18d.tar.gz .tar.gz
++ echo bokeh-3.5.0.dev1+27.g0aeab18d
+ export VERSION=3.5.0.dev1+27.g0aeab18d
+ VERSION=3.5.0.dev1+27.g0aeab18d

But in the lastest failing ones that is not the case

++++ ls dist/bokeh-3.5.dev1+36.gc297d210.tar.gz
+++ basename dist/bokeh-3.5.dev1+36.gc297d210.tar.gz .tar.gz
++ echo bokeh-3.5.dev1+36.gc297d210
+ export VERSION=3.5.dev1+36.gc297d210
+ VERSION=3.5.dev1+36.gc297d210

Best guess is the new setuptools release from 4 hours ago has decided to drop .0 point versions when build is run. Unfortunately the build job does not dump its package list so it's impossible to compare to successful jobs (we should fix that too).

Assuming we determine the problem is in fact new setuptools, we have a few options:

• pin setuptools version 👎
• change the strict string comparison in bokeh.util.package to a proper version compare
• check with upstream to see if there is a way to restore the old behavior (or see if it is a bug)

[bryevdv]

And in fact today's setuptools releases have been yanked:

[bryevdv]

ref: pypa/setuptools#4302

[bryevdv]

This was resolved upstream