Skip to content

Commit

Permalink
Merge pull request #2028 from CliMA/ck/bump_patches
Browse files Browse the repository at this point in the history
Bump patch versions/compats, update the news
  • Loading branch information
charleskawczynski authored Oct 3, 2024
2 parents 734f8a9 + b9cf80b commit de631af
Show file tree
Hide file tree
Showing 4 changed files with 14 additions and 8 deletions.
16 changes: 11 additions & 5 deletions NEWS.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@ ClimaCore.jl Release Notes
main
-------

- Defined some convenience methods [#2012](https://github.com/CliMA/ClimaCore.jl/pull/2012)

v0.14.17
v0.14.18
-------

- Fixed some type instabilities PR [#2004](https://github.com/CliMA/ClimaCore.jl/pull/2004)
- More fixes to higher resolution column cases for the GPU [#1854](https://github.com/CliMA/ClimaCore.jl/pull/1854)
- Fixed multiple-field solve for land simulations PR [#2025](https://github.com/CliMA/ClimaCore.jl/pull/2025).
- Fixed Julia 1.11 PR [#2018](https://github.com/CliMA/ClimaCore.jl/pull/2018).
- `Nh` was turned back into a dynamic parameter, in order to alleviate compile times PR [#2005](https://github.com/CliMA/ClimaCore.jl/pull/2005).
- Defined some convenience methods [#2012](https://github.com/CliMA/ClimaCore.jl/pull/2012)

### ![][badge-🐛bugfix] Fix equality for `FieldVector`s with different type

Expand All @@ -31,6 +31,12 @@ one.

PR [#2021](https://github.com/CliMA/ClimaCore.jl/pull/2021).

v0.14.17
-------

- Fixed some type instabilities PR [#2004](https://github.com/CliMA/ClimaCore.jl/pull/2004)
- More fixes to higher resolution column cases for the GPU [#1854](https://github.com/CliMA/ClimaCore.jl/pull/1854)

v0.14.16
-------

Expand Down
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "ClimaCore"
uuid = "d414da3d-4745-48bb-8d80-42e94e092884"
authors = ["CliMA Contributors <clima-software@caltech.edu>"]
version = "0.14.17"
version = "0.14.18"

[deps]
Adapt = "79e6a3ab-5dfb-504d-930d-738a2a938a0e"
Expand Down
2 changes: 1 addition & 1 deletion lib/ClimaCorePlots/Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "ClimaCorePlots"
uuid = "cf7c7e5a-b407-4c48-9047-11a94a308626"
authors = ["CliMA Contributors <clima-software@caltech.edu>"]
version = "0.2.11"
version = "0.2.12"

[deps]
ClimaComms = "3a4d1b5c-c61d-41fd-a00a-5873ba7a1b0d"
Expand Down
2 changes: 1 addition & 1 deletion lib/ClimaCoreTempestRemap/Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "ClimaCoreTempestRemap"
uuid = "d934ef94-cdd4-4710-83d6-720549644b70"
authors = ["CliMA Contributors <clima-software@caltech.edu>"]
version = "0.3.17"
version = "0.3.18"

[deps]
ClimaComms = "3a4d1b5c-c61d-41fd-a00a-5873ba7a1b0d"
Expand Down

6 comments on commit de631af

@charleskawczynski
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
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/116534

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

@charleskawczynski
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 subdir=lib/ClimaCorePlots

@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/116535

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 ClimaCorePlots-v0.2.12 -m "<description of version>" de631af2320d640556136cebf3cafc8e3cf26709
git push origin ClimaCorePlots-v0.2.12

Also, note the warning: Version 0.2.12 skips over 0.2.11
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@charleskawczynski
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 subdir=lib/ClimaCoreTempestRemap

@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/116536

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 ClimaCoreTempestRemap-v0.3.18 -m "<description of version>" de631af2320d640556136cebf3cafc8e3cf26709
git push origin ClimaCoreTempestRemap-v0.3.18

Please sign in to comment.