Repository navigation
[CHORE] Release 0.5.0 - #104
Merged
Merged
Conversation
…1 target, oxygen registry, migration notes, docs workflows)
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Add regression coverage for the second-sensor oxygen registration and address the documentation/changelog findings.
3 open findings
What changed in this PR
Prepares the 0.5.0 release with metadata, tooling, documentation, CI, and dissolved-oxygen registry updates.
Changes:
- Updates release metadata, changelog, and migration guidance.
- Aligns Python/Ruff targets and modernizes UTC usage.
- Registers the second oxygen variable and removes notebook error suppression.
| File | Description |
|---|---|
pyproject.toml |
Raises Ruff target to Python 3.11. |
oceanarray/reports/_recovery_table.py |
Uses datetime.UTC. |
oceanarray/reports/_mooring.py |
Uses datetime.UTC. |
oceanarray/reports/_instrument.py |
Uses datetime.UTC. |
oceanarray/reports/_html_helpers.py |
Uses datetime.UTC. |
oceanarray/reports/_array.py |
Uses datetime.UTC. |
oceanarray/config/parameters.py |
Registers second-sensor oxygen units. |
docs/source/migration.rst |
Adds 0.4-to-0.5 migration guidance. |
CITATION.cff |
Updates release version and date. |
CHANGELOG.md |
Adds 0.5.0 release notes and known issues. |
.github/workflows/pypi.yml |
Pins publishing to Python 3.13. |
.github/workflows/docs.yml |
Removes notebook error suppression. |
.github/workflows/docs_deploy.yml |
Removes notebook error suppression. |
🧠 Review effort: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…migration link, remove MIGRATION-BASEDIR.md, changelog and docs corrections
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.


Summary
Release prep for 0.5.0: version and date bumps, the PyPI workflow pinned to Python 3.13, the ruff target raised to match the 3.11 floor, the
dissolved_oxygen_ml_l_2registry entry, an "Upgrading from 0.4 to 0.5" migration subsection, two docs-workflow cleanups, and the CHANGELOG assembled with the breaking changes and known issues.What's changed
[Unreleased]→[0.5.0] — 2026-10-12(fresh empty[Unreleased]kept on top); added entries for [FEAT] Vendored masthead nav — re-vendor the report-design files and build the nav from the shared macro #100 (shared masthead nav), [FIX] Refuse colliding instrument serials before processing #101 (serial uniqueness) and [REFACTOR] Report inventory tables (coordinates + attribute disclosure), canonical-unit fixture, demo-notebook cleanup #103 (report inventory tables + canonical-unit fixture + notebook cleanup); the existing [FEAT] One netCDF writer for the processing stages #98/[REFACTOR] Writer cleanup — drop dead helpers, pin time, drop None attributes #99/[FIX] Write canonical units at every stage and refuse unknown ones #102 entries and the Breaking block are kept; a Known issues section records the turbidity empty-units skip-with-ERROR behaviour and the dune2 fixture stack/grid orphan.CITATION.cff: version 0.5.0, date-released 2026-10-12..github/workflows/pypi.yml:python-versionpinned"3.x"→"3.13"("3.x"resolved 3.15 with no h5py wheel).pyproject.toml: rufftarget-versionpy310→py311(agreeing withrequires-python >= 3.11); the fiveUP017auto-fixes it surfaces (datetime.timezone.utc→datetime.UTC) are applied inreports/_array.py,_html_helpers.py,_instrument.py,_mooring.py,_recovery_table.py.docs/source/migration.rst: an "Upgrading from 0.4 to 0.5" subsection at the top — reprocess from stage 1 for distributed files;save_dataset/save_OS_instrument→writers.write; pinned time encoding moves raw stored values ≤ 128 ns;processruns stages 1–3 by default. The layout guide stays below.oceanarray/config/parameters.py: registerdissolved_oxygen_ml_l_2(the SBEsbeox1ML/Lsecond-sensor mL/L reading) so the units pass canonicalises it instead of leaving it untouched..github/workflows/docs.yml,docs_deploy.yml: drop--ExecutePreprocessor.allow_errors=Truefrom thedemo_mooringnbconvert step — the notebook runs clean on the committed fixture (verified), so the flag only hid a future break.Breaking changes
None new in this PR. It assembles the 0.5.0 CHANGELOG whose breaking entries (#99 writer removal + Python 3.11, #102 canonical units) landed in their own PRs.
Tests
Full suite 1066 passed / 8 skipped; ruff clean under
py311; theUP017diff is datetime-only; sphinx buildsmigration.rstwithout warnings;demo_mooringwas executed clean before droppingallow_errors.