Skip to content

Prepare for release of PyNWB 4.2.0 (take two) - #2261

Merged
rly merged 4 commits into
devfrom
rel/4.2.0-take-two
Sep 2, 2026
Merged

Prepare for release of PyNWB 4.2.0 (take two)#2261
rly merged 4 commits into
devfrom
rel/4.2.0-take-two

Conversation

@rly

@rly rly commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Re-cut of 4.2.0 after the first tag failed to publish.

Checklist notes: all 15 PRs merged since 4.1.0 are represented in the changelog; the awk extraction yields 25 non-empty lines of release notes; the nwb-schema submodule is at the 2.11.0 tag; legal dates already read 2017-2026. Local tests and docs were not run, CI covers them.

🤖 Generated with Claude Code

rly and others added 2 commits September 2, 2026 14:01
The 4.2.0 tag build produced a wheel with Metadata-Version 2.5, which
hatchling 1.32.0 emits by default. pypa/gh-action-pypi-publish v1.14.1
pins twine 6.1.0 and packaging 25.0, which recognize metadata versions
up to 2.4 only, so the upload step failed with InvalidDistribution and
the release did not publish. v1.14.2 pins twine 7.0.0 and packaging
26.2, which accept 2.5.

Add a "Check distribution metadata" step alongside every step that
builds a distribution, running the same twine version the publish
action bundles, so a pull request fails on metadata that the upload
would reject. Record the pin coupling on the publish step and in the
release checklist.

Pin numcodecs in environment-ros3.yml. numcodecs publishes no cp314
wheel within the bound the zarr extra sets, so pip compiled the sdist
inside the conda environment, where the conda-forge python's CFLAGS
reach gcc as an unrecognized -partition=none. conda-forge has a
prebuilt 0.15.1 for python 3.14 on linux-64.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Set the 4.2.0 release date to September 2, 2026.

Point three changelog entries at the pull requests that made the
change instead of the issues they closed, matching the rest of the
file.

Update actions/setup-python to v7 and astral-sh/ruff-action to v4,
the latest releases. setup-python v7 drops the pip-install input,
which no workflow here uses; ruff-action v4 moves to node24, which
affects self-hosted runners only. Every other action already
references its latest major.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@codecov

codecov Bot commented Sep 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.17%. Comparing base (ddcbee3) to head (de08ace).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #2261   +/-   ##
=======================================
  Coverage   96.17%   96.17%           
=======================================
  Files          30       30           
  Lines        3003     3003           
  Branches      437      437           
=======================================
  Hits         2888     2888           
  Misses         65       65           
  Partials       50       50           
Flag Coverage Δ
integration 75.02% <ø> (ø)
unit 86.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

ruff-action publishes immutable releases from v4 onward, so no moving
v4 tag exists to reference.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Base automatically changed from fix/pypi-publish-metadata-2.5 to dev September 2, 2026 21:25
@rly
rly marked this pull request as ready for review September 2, 2026 21:26
@rly
rly requested a review from oruebel September 2, 2026 21:26
@rly
rly merged commit 8676056 into dev Sep 2, 2026
69 checks passed
@rly
rly deleted the rel/4.2.0-take-two branch September 2, 2026 22:07
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