Merge branch 'main' into feat/numcodecs-compat

Author: d-v-b

.github/ISSUE_TEMPLATE/release-checklist.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-**Release**: [v0.x.x](https://github.com/zarr-developers/zarr-python/milestones/?)
+**Release**: [v3.x.x](https://github.com/zarr-developers/zarr-python/milestones/?)
 **Scheduled Date**: 20YY/MM/DD
 
 **Priority PRs/issues to complete prior to release**
@@ -16,8 +16,9 @@ assignees: ''
 
 **Before release**:
 
+- [ ] Make sure the release branch (e.g., `3.1.x`) is up to date with any backports.
 - [ ] Make sure that all pull requests which will be included in the release have been properly documented as changelog files in the [`changes/` directory](https://github.com/zarr-developers/zarr-python/tree/main/changes).
-- [ ] Run ``towncrier build --version x.y.z`` to create the changelog, and commit the result to the main branch.
+- [ ] Run ``towncrier build --version x.y.z`` to create the changelog, and commit the result to the release branch.
 - [ ] Check [SPEC 0](https://scientific-python.org/specs/spec-0000/#support-window) to see if the minimum supported version of Python or NumPy needs bumping.
 - [ ] Check to ensure that:
   - [ ] Deprecated workarounds/codes/tests are removed. Run `grep "# TODO" **/*.py` to find all potential TODOs.
@@ -41,6 +42,7 @@ assignees: ''
 - [ ] Go to https://github.com/zarr-developers/zarr-python/releases.
   - [ ] Click "Draft a new release".
   - [ ] Choose a version number prefixed with a `v` (e.g. `v0.0.0`). For pre-releases, include the appropriate suffix (e.g. `v0.0.0a1` or `v0.0.0rc2`).
+  - [ ] Set the target branch to the release branch (e.g., `3.1.x`)
   - [ ] Set the description of the release to: `See release notes https://zarr.readthedocs.io/en/stable/release-notes.html#release-0-0-0`, replacing the correct version numbers. For pre-release versions, the URL should omit the pre-release suffix, e.g. "a1" or "rc1".
   - [ ] Click on "Generate release notes" to auto-fill the description.
   - [ ] Make a release by clicking the 'Publish Release' button, this will automatically create a tag too.

.github/workflows/check_changelogs.yml

@@ -0,0 +1,18 @@
+name: Check changelog entries
+
+on:
+  pull_request:
+
+jobs:
+  check-changelogs:
+    name: Check changelog entries
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc # v6.4.3
+
+      - name: Check changelog entries
+        run: uv run --no-sync python ci/check_changelog_entries.py

.github/workflows/gpu_test.yml

@@ -5,9 +5,9 @@ name: GPU Test
 
 on:
   push:
-    branches: [ main ]
+    branches: [ main, 3.1.x ]
   pull_request:
-    branches: [ main ]
+    branches: [ main, 3.1.x ]
   workflow_dispatch:
 
 env:

.github/workflows/hypothesis.yaml

@@ -1,9 +1,9 @@
 name: Slow Hypothesis CI
 on:
   push:
-    branches: [main, 3.0.x]
+    branches: [main, 3.1.x]
   pull_request:
-    branches: [main, 3.0.x]
+    branches: [main, 3.1.x]
     types: [opened, reopened, synchronize, labeled]
   schedule:
     - cron: "0 0 * * *" # Daily “At 00:00” UTC

.github/workflows/test.yml

@@ -5,9 +5,9 @@ name: Test
 
 on:
   push:
-    branches: [ main, 3.0.x ]
+    branches: [ main, 3.1.x ]
   pull_request:
-    branches: [ main, 3.0.x ]
+    branches: [ main, 3.1.x ]
   workflow_dispatch:
 
 concurrency:

LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015-2024 Zarr Developers <https://github.com/zarr-developers>
+Copyright (c) 2015-2025 Zarr Developers <https://github.com/zarr-developers>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

changes/3083.feature.rst

@@ -0,0 +1 @@
+Added support for async vectorized and orthogonal indexing.

changes/3251.fix.rst renamed to changes/3251.bugfix.rst

@@ -0,0 +1,4 @@
+- Expand the range of types accepted by ``parse_data_type`` to include strings and Sequences.
+- Move the functionality of ``parse_data_type`` to a new function called ``parse_dtype``. This change
+  ensures that nomenclature is consistent across the codebase. ``parse_data_type`` remains, so this
+  change is not breaking.