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

prepare for geo-0.24.0 release #990

Merged
merged 1 commit into from
Mar 8, 2023
Merged

prepare for geo-0.24.0 release #990

merged 1 commit into from
Mar 8, 2023

Conversation

michaelkirk
Copy link
Member

@michaelkirk michaelkirk commented Mar 6, 2023

  • I agree to follow the project's code of conduct.
  • I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

Note: this depends on #989 being released first Update: released!

Anything else we should be waiting on before a geo-0.24.0 release?

@michaelkirk michaelkirk changed the title Release/0.24.0 prepare for geo-0.24.0 release Mar 6, 2023
@@ -1,6 +1,6 @@
# Changes

## unreleased
Copy link
Member

Choose a reason for hiding this comment

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

this is the wrong changelog change

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch! I've updated the geo CHANGES file.

(note that this PR still contains updates to the geo-types CHANGES file by virtue of it being based on #989)

@michaelkirk
Copy link
Member Author

I'll plan to wait on #991 (which seems straight forward) before releasing geo 0.24.0

@michaelkirk
Copy link
Member Author

bors r+

@bors
Copy link
Contributor

bors bot commented Mar 8, 2023

Build succeeded:

@bors bors bot merged commit f16f114 into main Mar 8, 2023
@bors bors bot deleted the release/0.24.0 branch March 8, 2023 20:04
@michaelkirk
Copy link
Member Author

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.

2 participants