Skip to content

Release version 1.3.2 - #53

Merged
sirosen merged 1 commit into
pypa:mainfrom
sirosen:release-1.3.2
Aug 22, 2026
Merged

sirosen merged 1 commit into
pypa:mainfrom
sirosen:release-1.3.2

Conversation

@sirosen

@sirosen sirosen commented Aug 13, 2026 •

Copy link
Copy Markdown
Contributor

Changelog

This is the changelog from v1.3.2 , verbatim, at time of writing.

  • Add support for Python 3.14 and 3.15
  • Remove support for Python 3.8
  • Correct the type of the dependency_groups parameter to resolve(),
    resolve_all(), and DependencyGroupsResolver().
  • Raise a clear TypeError when an include-group value is not a string
    (was a cryptic TypeError from name normalization), and accept any
    Mapping for include items, not only dict.
  • Fix a bug in which pip-install-dependency-groups failed when the
    resolved groups were empty. It now prints Nothing to install and exits
    normally.
  • dependency-groups --list now respects the -o/--output option.

Minor vs Patch

I decided on a patch release, as there are no new features. Only fixes and Python support updates.

Aside: Process

@henryiii I gave it a short rest (since the last change) before prepping this, and then went over the release process for this repo to push this out.

I noticed some process/meta things:

  • there isn't a documented process at all (!), not even a super short 3-line RELEASING.md -- I plan to add one, just so the mechanism is documented
  • the last release (1.3.1) was done in the style of a solo maintainer; I'd like to switch to using release PRs like this one
  • the current publishing flow is
    • tag triggers Test PyPI workflow
    • GitHub release triggers PyPI workflow

That setup (tag and release triggers) is the way I do things for most of my independent projects, but I can adapt if there are changes you think we/I should make.

After approval, I'll merge, tag, and create the release. :)


📚 Documentation preview 📚: https://dependency-groups--53.org.readthedocs.build/en/53/

@henryiii henryiii left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The pytest config PR went in if you wanted to mention that, otherwise looks good. Release system makes sense I think.

@sirosen

sirosen commented Aug 22, 2026

Copy link
Copy Markdown
Contributor Author

The pytest config PR went in if you wanted to mention that

I'd probably be 50/50 on it if I didn't have the release PR already open. 😁
Since you're not actively advocating for it, I'll leave it out for convenience's sake.

@sirosen
sirosen merged commit d21c4fb into pypa:main Aug 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants