Prepare 2.11.0 release - #710
Merged
Merged
Conversation
Update the hdmf-common-schema submodule from 1.9.0 to 1.10.0, set the version string to 2.11.0 in conf.py, nwb.namespace.yaml, and nwb.file.yaml, and set the release notes heading to "2.11.0 (August 20, 2026)". The release is 2.11.0 rather than 2.10.1 because three changes since 2.10.0 are above patch level: the new optional Units.waveform_*.time_before_peak_in_ms attribute, the relaxation of the waveform unit attribute from a fixed value to a default value, and the hdmf-common-schema 1.10.0 change of MeaningsTable.target from a link to an object-reference attribute. Move the waveform unit entry in the release notes from "Bug fixes" to "Minor changes", since widening what the schema accepts is a schema feature change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
oruebel
previously approved these changes
Aug 19, 2026
Contributor
Author
|
@ehennestad Could you please test matnwb with the schema in this branch? |
Contributor
Will check by the end of the day |
Contributor
Author
|
Thanks! I don't expect any issues. But also, no need to rush this. |
Contributor
Looks good, no issues for MatNWB |
Contributor
Author
|
Thanks @ehennestad for the quick confirmation! |
oruebel
approved these changes
Aug 21, 2026
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Target release date: August 20, 2026
Bumped from the previously planned 2.10.1 to 2.11.0. This release adds a new optional attribute (
Units.waveform_*.time_before_peak_in_ms), relaxes the fixedunitattribute on the waveform datasets to a default value, and incorporates hdmf-common-schema 1.10.0, which contains a breaking change toMeaningsTable.target. None of these are patch-level changes under the NWB Extensions Versioning Guidelines.Before merging:
requirements-doc.txtdeps are unpinned)Legal.txt,license.txt,README.md,docs/format/source/conf.py, and any other locations as needed (all already read 2017-2026)README.rstas needed (no changes needed)docs/format/source/conf.py,core/nwb.namespace.yaml, andcore/nwb.file.yaml(remove "-alpha" suffix)docs/format/source/conf.pyas neededdocs/format/source/format_release_notes.rstand any other docs as neededcd docs/format; make fulldoc) and check for warnings and errors (HTML build succeeds with no warnings; thelatexpdfstep needslatexmk, which is not installed locally)Changes in this PR
hdmf-common-schemasubmodule from 1.9.0 (497bde3) to 1.10.0 (e7f84f0).2.11.0indocs/format/source/conf.py,core/nwb.namespace.yaml, andcore/nwb.file.yaml.2.11.0 (August 20, 2026)and added a "Major changes" entry for the hdmf-common-schema 1.10.0MeaningsTable.targetchange.unitchange from "Bug fixes" to "Minor changes". Changingvalue: voltstodefault_value: voltswidens what the schema accepts, so it is a schema feature change rather than a bug fix.Why 2.11.0 and not 2.10.1
Three changes since 2.10.0 are above patch level:
time_before_peak_in_msis a new optional attribute onUnits.waveform_mean,Units.waveform_sd, andUnits.waveforms. New optional fields have gone into minor releases (e.g.ImageSeries.num_samplesin 2.10.0).unitattribute on those same datasets went from a fixedvalueofvoltsto adefault_valueofvolts. A file written under this schema with a non-volts unit does not validate against 2.10.0.MeaningsTable.targetfrom a link to an object-reference attribute. The hdmf-common release notes label this a breaking change for files written with the 1.9.0 definition.Every prior patch release of nwb-schema (2.2.1 through 2.2.5) contained only typo fixes, doc corrections, and non-functional restructuring. This release does not fit that pattern.
Item 3 is the one worth discussing on its own. A breaking change to an existing data type would normally call for a major version bump.
MeaningsTableshipped for the first time in NWB 2.10.0 two months ago, so the population of files using the 1.9.0 layout should be very small, and a minor bump is the proportionate response. If any published data is known to useMeaningsTable, this decision should be revisited before merging.After merging:
git tag 2.11.0 --sign, copy and paste the release notes into the tag message, and rungit push --tags.See https://nwb-schema.readthedocs.io/en/latest/software_process.html for more details.
🤖 Generated with Claude Code