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

Release to pin cirrus-geo stable #11

Closed
wants to merge 1 commit into from

Conversation

ircwaves
Copy link
Member

No description provided.

@ircwaves ircwaves requested a review from jkeifer May 13, 2024 21:56
@@ -5,6 +5,16 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).

## [v0.1.2] - 2024-02-16
Copy link
Member

Choose a reason for hiding this comment

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

Wrong date

@jkeifer
Copy link
Member

jkeifer commented May 14, 2024

The tests failed, it looks like this project needs some changes to be compatible with the latest cirrus-geo v0 release. I agree with the upper bound on the pinning but I don't think this can be released in the current state. I'm not sure if you are intending to create another PR to address those problems but it looked like this was a release-prep PR, so I haven't clicked the approve button just yet.

@ircwaves
Copy link
Member Author

The tests failed, it looks like this project needs some changes to be compatible with the latest cirrus-geo v0 release. I agree with the upper bound on the pinning but I don't think this can be released

Yeah, this looks dead for sure. I'll cut a new one when the changes are in to update to be v0.15.x compatible. Does feel like that is a non-trivial update here,

@ircwaves ircwaves closed this May 14, 2024
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