Repository navigation
fix(docs): update documentation to reflect GeoZarr conventions - #230
Merged
Merged
Conversation
…across documentation
Contributor
Security Audit ReportBandit — Static Security Analysis (Security tab)9 issue(s) found: 9 low ✅ No issues at or above HIGH severity. 9 low issue(s) below threshold not shown in table. pip-audit — Dependency Vulnerabilities (Security tab)
3 vulnerability/vulnerabilities found (3 fixable) across 1 package(s). Result: ❌ Blocking issues found — see details above. |
Contributor
|
I'm going to approve and merge despite the security audit failing. none of those aiohttp vulnerabilities are applicable to this repo. |
d-v-b
approved these changes
Aug 10, 2026
Merged
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.
Revise all documentation references from GeoZarr-spec 0.4 to GeoZarr format, aligning with the current conventions and clarifying the library's compliance with the evolving GeoZarr standards.