Use setuptools-scm to determine versions

[mdboom]

This uses the setuptools-scm package to automatically determine the version of each package from the corresponding git tag.

This is motivated by a couple of things:

• Removing more steps in our release project (in this case, manually updating version numbers)
• Making the version number of work on main always be greater than the latest release, so we can dynamically turn on new features in cuda.core based on in-development work in cuda.bindings.

From an offline discussion with @leofang, we have a requirement here that release candidate builds can be shipped as-is as final releases. Therefore, the tag matching regexes have been written so that:

tag	version
v13.1.1rc1	13.1.1
v13.1.1	13.1.1
(no tag)	13.1.2.dev34+gecfc79fb9

This does have the downside that the first and second builds above, even if the hashes the tags point at are different, will have the same filename. The builds will be distinguishable by inspecting cuda.bindings._version.__commit_id__, however.

Other implications of this change:

Packages that are locally installed from git from an untagged commit will have complicated-but-helpful version numbers like 13.1.2.dev34+gecfc79fb9, so parsing them is a little more complicated than .split('.'). To help with that, setuptools-scm also generates a version_tuple that dependent projects can use:

__version__ = version = '13.1.2.dev34+gecfc79fb9'
__version_tuple__ = version_tuple = (13, 1, 2, 'dev34', 'gecfc79fb9')
__commit_id__ = commit_id = 'gecfc79fb9'

but that should only effect developers installing non-released versions of our software. People installing from official packages should continue to see simple version numbers.

Building from an sdist continues to work -- the tarball will contain the generated _version.py files, and will be (as it should be) hardcoded with the version that the sdist was generated from.

[copy-pr-bot]

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[mdboom]

/ok to test

[mdboom]

/ok to test

[mdboom]

/ok to test

[mdboom]

/ok to test

[cryos]

Great to see this, I had been meaning to ask about adding in dynamic versioning. It feels a little odd hiding the rc suffix, but all projects are different. A huge step forward, thanks for working on this! Curious why we wouldn't tag and rebuild but that is orthogonal to whether this should be merged.

[mdboom]

/ok to test

[rwgk]

I'm also a bit worried about doing something unusual for the rc suffix (my general thinking: "every wrinkle we add is a stumbling hazard") but our constraints are also unusual. Overall, this looks like a big step in the right direction, I think we should give this a try and fix forward as needed.

[mdboom]

/ok to test

[mdboom]

/ok to test

[mdboom]

/ok to test

[mdboom]

/ok to test

[mdboom]

Cc: @leofang, @cryos. Dismissed the approval because I had to make a couple more changes to get CI to pass. Also see the backport of this to the 12.9.x branch in #1415.

[mdboom]

/ok to test

[mdboom]

/ok to test

[github-actions]

Backport failed for 12.9.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 12.9.x
git worktree add -d .worktree/backport-1411-to-12.9.x origin/12.9.x
cd .worktree/backport-1411-to-12.9.x
git switch --create backport-1411-to-12.9.x
git cherry-pick -x da7eb1f5a97aa21d8f78098e13e7c4edad013530

[github-actions]

Doc Preview CI
Preview removed because the pull request was closed or merged.

[leofang]

Cc: @leofang, @cryos. Dismissed the approval because I had to make a couple more changes to get CI to pass. Also see the backport of this to the 12.9.x branch in #1415.

@mdboom sorry I could not respond promptly. I see the automerge kicked in and this PR is now merged -- is it intended?

[leofang]

Overall, this looks like a big step in the right direction, I think we should give this a try and fix forward as needed.

Yes, this was also the conclusion we reached on the Thursday team-sync.

[leofang]

Thanks for the bug fix!

[github-actions]

Backport failed for 12.9.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 12.9.x
git worktree add -d .worktree/backport-1411-to-12.9.x origin/12.9.x
cd .worktree/backport-1411-to-12.9.x
git switch --create backport-1411-to-12.9.x
git cherry-pick -x da7eb1f5a97aa21d8f78098e13e7c4edad013530

[github-actions]

Backport failed for 12.9.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 12.9.x
git worktree add -d .worktree/backport-1411-to-12.9.x origin/12.9.x
cd .worktree/backport-1411-to-12.9.x
git switch --create backport-1411-to-12.9.x
git cherry-pick -x da7eb1f5a97aa21d8f78098e13e7c4edad013530

[github-actions]

Backport failed for 12.9.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 12.9.x
git worktree add -d .worktree/backport-1411-to-12.9.x origin/12.9.x
cd .worktree/backport-1411-to-12.9.x
git switch --create backport-1411-to-12.9.x
git cherry-pick -x da7eb1f5a97aa21d8f78098e13e7c4edad013530

[github-actions]

Backport failed for 12.9.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 12.9.x
git worktree add -d .worktree/backport-1411-to-12.9.x origin/12.9.x
cd .worktree/backport-1411-to-12.9.x
git switch --create backport-1411-to-12.9.x
git cherry-pick -x da7eb1f5a97aa21d8f78098e13e7c4edad013530

[github-actions]

Backport failed for 12.9.x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin 12.9.x
git worktree add -d .worktree/backport-1411-to-12.9.x origin/12.9.x
cd .worktree/backport-1411-to-12.9.x
git switch --create backport-1411-to-12.9.x
git cherry-pick -x da7eb1f5a97aa21d8f78098e13e7c4edad013530