zarr-developers/VirtualiZarr

AI Summary: This issue proposes decoupling the `minimum-versions` workflow from the `test-upstream` label. Currently, `minimum-versions` only runs when `test-upstream` is applied, but it should run on every pull request. This is because `minimum-versions` tests are not slow and are crucial for ensuring compatibility with older dependencies, unlike `upstream` tests which are slow and only relevant for development against unreleased versions.

AI Summary: The task is to refactor the `icechunk.py` file in the VirtualiZarr project to eliminate unnecessary type conversions between Zarr data types and NumPy dtypes. Specifically, the code at line 347 should be modified to directly use `metadata.data_type` instead of performing an intermediate conversion.

AI Summary: Modify the CI/CD pipeline for the VirtualiZarr project to trigger the documentation build process even for pull requests that only change documentation files. This ensures that documentation updates are always built and tested, improving the overall quality and reliability of the project's documentation.

AI Summary: Improve the layout and usability of the VirtualiZarr API documentation page on ReadTheDocs. The current page presents all API elements in a long, unorganized list, making it difficult to navigate. The task involves restructuring the documentation to improve readability and searchability, potentially using a table of contents, subsections, or a more concise presentation style similar to xarray's API documentation.

AI Summary: Update the documentation's homepage example to reflect the changes in the V2 API. This involves creating a runnable code example using Python and xarray, ensuring it executes correctly during the documentation build process, and replacing the existing outdated example.

AI Summary: Update the VirtualiZarr migration guide's documentation to reflect the new ObjectStoreRegistry API, using executable code examples within the documentation that leverage the `exec="on"` and `session` features of the documentation builder to ensure consistent execution and avoid code duplication.

AI Summary: Update the VirtualiZarr documentation's 'custom parsers' page to reflect the new API, specifically instructing users to utilize the `ObjectStoreRegistry` as input for the parser. This involves modifying the existing documentation to accurately represent the updated functionality.

AI Summary: Update the examples on the VirtualiZarr documentation's scaling page to reflect the new API, ensuring the code snippets are executable and verified using the instructions from issue #690.

AI Summary: Update the Frequently Asked Questions (FAQ) section of the VirtualiZarr documentation to reflect changes in the API. This involves modifying existing code examples to use the new API and ensuring they remain executable and verifiable using the instructions provided in issue #690.

AI Summary: Update the VirtualiZarr documentation's usage guide to reflect the new API. This involves rewriting examples using a specific Sphinx code block format that executes the code during the documentation build, allowing for live, tested examples. The examples should be concise and illustrative of the new API's functionality.

AI Summary: Debug and fix two issues within the VirtualiZarr CI/CD pipeline: 1) Ensure that `upstream-tests` run on every push to a pull request, not just when the label is applied; and 2) Prevent the cancellation of subsequent test jobs when one fails, allowing all jobs to complete for comprehensive diagnostic information.

AI Summary: Implement alternate tabbed code blocks in VirtualiZarr's MkDocs documentation using the `pymdownx.tabbed` extension, specifically enabling the `alternate_style` option to improve readability and user experience when presenting multiple code examples (e.g., local vs. S3 storage options).

AI Summary: Implement a warning mechanism within the VirtualiZarr library to alert users when attempting to serialize an xarray Dataset that doesn't contain any virtual arrays. This involves modifying the existing serialization process to check for the presence of virtual arrays and issue a warning if none are found.

AI Summary: Integrate the Towncrier bot into the VirtualiZarr project to automate the generation of release notes. This involves configuring the bot according to the project's needs and potentially adapting existing workflows to incorporate the generated notes.

AI Summary: Update the examples in the VirtualiZarr project to reflect the changes in syntax introduced in the V2 release. This involves migrating examples from the old V1 syntax folder to the new syntax, ensuring compatibility and functionality.

AI Summary: The task involves adding cross-links to the VirtualiZarr documentation for various dependencies (xarray, NumPy, numcodecs, Zarr, and Obstore), both required and optional, and implementing a CI check to ensure the documentation build process doesn't produce any warnings. This ensures all links are valid and the documentation is consistently well-maintained.