build: Pass in the build version explicitly.

This means we're using setuptools_scm in a very dumb and limited way but
it does reduce boilerplate files/code in this repo and that project is
fairly stable so I think it's fine.

Ideally we either switch to a different build system in the future or
the setuptools build interface allows for us to override the version
number at build time.

Author: feanil

backend/pyproject.toml

@@ -45,7 +45,12 @@ include = ["sample_plugin*"]
 exclude = ["sample_plugin.tests*"]
 
 [tool.semantic_release]
-build_command = "pip install build && python -m build"
+# We use SETUPTOOLS_SCM_PRETEND_VERSION to pull the version from python-semantic-release instead
+# of actually pulling it from version control because the build step happens before the repo gets
+# tagged. Setuptools by default doesn't have any way of overriding the version number at build
+# time without a setup.py file.  This is a fine alternative that reduces the amount of boilerplate
+# code and files we need in this repo.
+build_command = "pip install build && SETUPTOOLS_SCM_PRETEND_VERSION=$NEW_VERSION python -m build"
 
 [tool.semantic_release.commit_parser_options]
 # Because this repo is meant to be an example, docs changes are relevant