Skip to content

Commit

Permalink
add ZarrDatasets.jl to IntegrationTest.yml
Browse files Browse the repository at this point in the history
  • Loading branch information
@Alexander-Barth
Alexander-Barth committed Feb 16, 2024
1 parent 34b114a commit 0c122c4
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions .github/workflows/IntegrationTest.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ jobs:
- {user: Alexander-Barth, repo: NCDatasets.jl}
- {user: JuliaGeo, repo: GRIBDatasets.jl}
- {user: Alexander-Barth, repo: TIFFDatasets.jl}
- {user: JuliaGeo, repo: ZarrDatasets.jl}

steps:
- uses: actions/checkout@v4
Expand Down

2 comments on commit 0c122c4

@Alexander-Barth
Copy link
Member Author

Choose a reason for hiding this comment

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

@JuliaRegistrator register

Release notes

  • experimental MemoryDataset implementation
  • in-place load! for multi-file datasets
  • parentdataset for the root group of a multi-file should be nothing
  • generic implementation for haskey for datasets
  • groupby for datasets

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/101029

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.5 -m "<description of version>" 0c122c4b48ca5aa8f12a03ff5ed6f23fac0164e4
git push origin v0.3.5

Please sign in to comment.