Skip to content

py-setuptools-scm: add v8.1.0, v8.2.0#49271

Merged
tldahlgren merged 3 commits intospack:developfrom
RobertMaaskant:py-setuptools-scm-v8.1.0-v8.2.0
Mar 13, 2025
Merged

py-setuptools-scm: add v8.1.0, v8.2.0#49271
tldahlgren merged 3 commits intospack:developfrom
RobertMaaskant:py-setuptools-scm-v8.1.0-v8.2.0

Conversation

@RobertMaaskant
Copy link
Copy Markdown
Contributor

And attempt to improve package definition based on upstream repo's pyproject.toml, setup.cfg, and setup.py.

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Mar 4, 2025

Hi @RobertMaaskant! I noticed that the following package(s) don't yet have maintainers:

  • py-setuptools-scm

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("RobertMaaskant")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame py-setuptools-scm

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

@RobertMaaskant RobertMaaskant changed the title WIP py-setuptools-scm: add v8.1.0, v8.2.0 py-setuptools-scm: add v8.1.0, v8.2.0 Mar 4, 2025
Copy link
Copy Markdown
Contributor

@tldahlgren tldahlgren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed the new sha256s.

@tldahlgren tldahlgren self-assigned this Mar 13, 2025
@tldahlgren tldahlgren merged commit 3bd58f3 into spack:develop Mar 13, 2025
16 checks passed
@RobertMaaskant RobertMaaskant deleted the py-setuptools-scm-v8.1.0-v8.2.0 branch March 13, 2025 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants