madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

Pin setuptools-scm build time dependency (#2457)
authorRichard Si <63936253+ichard26@users.noreply.github.com>
Sat, 28 Aug 2021 19:37:53 +0000 (15:37 -0400)
committerGitHub <noreply@github.com>
Sat, 28 Aug 2021 19:37:53 +0000 (15:37 -0400)
commita5bb6e0a320bf42f1b219ee2e55ea1c1917961dc
treec23d1202968e8473d87575911a512407a7c0c04c
parent7a093f0303c3fa7fee0b6742b7c6a3ff03438ace
Pin setuptools-scm build time dependency (#2457)

The setuptools-scm dependency in setup.cfg did not have a version
specified, leading to the issues described in #2449 after a faulty release
of setuptools-scm was published. To avoid this issue in the future, the
last version before that faulty update is now pinned.

Commit history before merge:

* Pin setuptools-scm dependency version (#2449)
* Update CHANGES.md
* Let's pin in pyproject.toml too

Mostly since it's non-build-backend specific configuration and more
widely standardized file. Not sure what benefits pinning in setup.cfg
gives us on top of pyproject.toml but I'd rather not find out during
the release that is supposed to happen today :wink:

Co-authored-by: FiNs <24248249+FabianNiehaus@users.noreply.github.com>
CHANGES.md
pyproject.toml
setup.cfg