Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JuliaRegistrator pings #35

Open
gaelforget opened this issue Jan 26, 2020 · 113 comments
Open

JuliaRegistrator pings #35

gaelforget opened this issue Jan 26, 2020 · 113 comments

Comments

@gaelforget
Copy link
Member

No description provided.

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/8501

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.2.5 -m "<description of version>" 4042c27f3a212c22cb5e0cb03c8605dd87ec80dd
git push origin v0.2.5

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/9173

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.2.6 -m "<description of version>" 67136859e3bb764d23b412b677c3c8a1e9177c96
git push origin v0.2.6

@gaelforget
Copy link
Member Author

@JuliaRegistrator register

Release notes:

  • add meta structure containing unit, position, and names
  • defaultmeta = varmeta(missing,fill(0.5,3),"unknown","unknown")
  • support for non-default varmeta is limited to constructors, similar, read and exchange
  • similar() uses defaultmeta by default -- unless optional argument m is provided (e.g. in read and exchanges)
  • fill in meta data for grid variables at the time when they are defined via read / similar / MeshArray() in GridLoad & GridOfOnes
  • show method now prints out meta for gcmarray
  • Project.toml now depends on Unitful.jl for varmeta data structure
  • rename mygrid,GridVariables as γ,Γ throughout packages
  • GridOfOnes now returns both γ,Γ
  • documentation updates/improvements

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/11665

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.2.7 -m "<description of version>" 7f36bd587e0f67f28259ea963181a97aeae30274
git push origin v0.2.7

@gaelforget
Copy link
Member Author

@JuliaRegistrator register

Release notes:

  • new (exported) functions knn, InterpolationFactors, and Tiles (which replaces TilesMap)
  • new dependency to NearestNeighbors.jl

Code follows my earlier gcmfaces implementation used with MITgcm and MITprof

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/12918

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.2.8 -m "<description of version>" d0b7a90768c1fd521d8b129c71c7f40a5181755a
git push origin v0.2.8

@gaelforget
Copy link
Member Author

@JuliaRegistrator register

Release notes:

  • fix edge cases in interpolation code
  • add Interpolate()
  • documentation updates

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/13057

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.2.9 -m "<description of version>" 48af511029b4919b003d2ffdd53b416af5b3f221
git push origin v0.2.9

@gaelforget
Copy link
Member Author

@JuliaRegistrator register

Release notes:

  • add InnerArray & OuterArray variables
  • InterpolationFactors -> local f,x,y position too

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/14903

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.2.10 -m "<description of version>" 360490f64e50a71f66aa79123697db6e73f2a933
git push origin v0.2.10

@gaelforget
Copy link
Member Author

@JuliaRegistrator register

Release notes:

  • add CompatHelper
  • (new) simple_periodic_domain
  • improve docs & add video links

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/90532

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.0 -m "<description of version>" dfcd6aac2da37a721cde539ff60bdc2c004481ca
git push origin v0.3.0

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/90827

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.1 -m "<description of version>" 00d9aa53112ceb2763207a4b76e157051cf060bd
git push origin v0.3.1

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/103994

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.2 -m "<description of version>" a73b283df039acd5ffe43a6ec784d5cb5e2adbe4
git push origin v0.3.2

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/104503

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.3 -m "<description of version>" d774ca5a485454558fcc6fb19114c6e9a4994728
git push origin v0.3.3

@gaelforget
Copy link
Member Author

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/107246

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.4 -m "<description of version>" 9c21d12c38a5ab1123c80b238944c1f40c2e7a43
git push origin v0.3.4

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/107267

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>" 02b6ba647319a07b4ea60f4d5e04735dec4acd6b
git push origin v0.3.5

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/107267

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>" 4b00fb6163b4b44162bcd9d4e91438252e0ef5d4
git push origin v0.3.5

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/107267

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>" 4b00fb6163b4b44162bcd9d4e91438252e0ef5d4
git push origin v0.3.5

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/107269

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.6 -m "<description of version>" 31aeb3da543eb74759e84d7ba6d8ad43e659f277
git push origin v0.3.6

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/107613

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.7 -m "<description of version>" bd5fe4e2703d0617cb008133e04b40d00995b403
git push origin v0.3.7

@gaelforget
Copy link
Member Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/107624

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.8 -m "<description of version>" 56fea962478a8bda47b7e70bf5cae8053e58d2f6
git push origin v0.3.8

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

No branches or pull requests

2 participants