Skip to content

Release v1#20

Closed
emmanuelmathot wants to merge 2 commits into
mainfrom
release/v1
Closed

Release v1#20
emmanuelmathot wants to merge 2 commits into
mainfrom
release/v1

Conversation

@emmanuelmathot

@emmanuelmathot emmanuelmathot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Release v1

Addresses #19 — the v1 tag has never been created, so the schema.json $id and all schema_url/spec_url fields point to a non-existent release, breaking external schema validation.

Changes

  • Fix organisation name in all URLs: The repository was transferred from zarr-experimental to zarr-conventions, but all schema_url, spec_url, and $id references still pointed to zarr-experimental/geo-proj. Updated across schema.json, README.md, and all example files.
  • Update package.json version to 1.0.0.

Next steps after merge

Create the v1 git tag on main so that the raw GitHub URLs referenced by the schema become resolvable:

git tag v1
git push origin v1

This will make https://raw.githubusercontent.com/zarr-conventions/geo-proj/refs/tags/v1/schema.json accessible for validators.

- Fix all schema_url and spec_url references from zarr-experimental to
  zarr-conventions organization (repo was transferred)
- Update package.json version to 1.0.0
- Update extension maturity classification from Proposal to Stable

Closes #19

@maxrjones maxrjones left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should publish v0.1, not v1, following the recommendations in zarr-developers/geozarr-spec#102 (comment) and zarr-conventions/zarr-conventions-spec#7 (comment) so that people do not misinterpret the stability of this convention and to defer the overall versioning decision to the next SWG meeting.

@emmanuelmathot

Copy link
Copy Markdown
Contributor Author

Happy to see we finally converge.

@maxrjones

Copy link
Copy Markdown
Contributor

FYI the attribute changed in this PR is unrelated to releasing v1; package.json defines a validation utility. Please see #24

@maxrjones

Copy link
Copy Markdown
Contributor

superseded by #26

@maxrjones maxrjones closed this Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release not available

2 participants