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

geo/geo bump proj to 0.27.0 #857

Merged
merged 3 commits into from Jun 24, 2022
Merged

geo/geo bump proj to 0.27.0 #857

merged 3 commits into from Jun 24, 2022

Conversation

martinfrances107
Copy link
Contributor

The is a ongoing discussion in #856 about how to signal to the wider community that our dependencies are changing.

But this is issue follows the pattern developed in #850

@michaelkirk
Copy link
Member

This LGTM, but I'm also not very concerned about publishing a breaking release for geo. I'd also be fine to just strictly bump proj without the range.

My position on this is different with geo-types - which is used across a lot of other crates. I'm much more willing to put effort into not breaking geo-types.

I'll wait until tomorrow to merge in case anyone else wants to weigh in.

@martinfrances107
Copy link
Contributor Author

I'd also be fine to just strictly bump proj without the range.

Great that is my preference..fixed.

@martinfrances107 martinfrances107 changed the title geo/geo bump the version of proj to include ">= 0.26.0, < 0.28.0". geo/geo bump proj to 0.27.0 Jun 24, 2022
@michaelkirk
Copy link
Member

bors r+

bors bot added a commit that referenced this pull request Jun 24, 2022
850: #849 Bump the minor version of approx. r=michaelkirk a=martinfrances107

- [x ] I agree to follow the project's [code of conduct](https://github.com/georust/geo/blob/main/CODE_OF_CONDUCT.md).
---

Consitently and in many Cargo.toml files  - bump the minor version of approx.


-approx = "0.4.0"
+approx = "0.5.1"

857: geo/geo bump  proj to 0.27.0 r=michaelkirk a=martinfrances107

The is a ongoing discussion in #856 about how to signal to the wider community that our dependencies are changing.

But this is issue follows the pattern developed in #850 



859: bump geojson to 0.23.0 r=michaelkirk a=martinfrances107

geojson is a internal dev-dependency.

860: Hide test artifact. r=michaelkirk a=martinfrances107

- [x] I agree to follow the project's [code of conduct](https://github.com/georust/geo/blob/main/CODE_OF_CONDUCT.md).
---

Alter .gitignore to remove a test artefact.


Co-authored-by: Martin <martinfrances107@hotmail.com>
@bors
Copy link
Contributor

bors bot commented Jun 24, 2022

Build failed (retrying...):

bors bot added a commit that referenced this pull request Jun 24, 2022
850: #849 Bump the minor version of approx. r=michaelkirk a=martinfrances107

- [x ] I agree to follow the project's [code of conduct](https://github.com/georust/geo/blob/main/CODE_OF_CONDUCT.md).
---

Consitently and in many Cargo.toml files  - bump the minor version of approx.


-approx = "0.4.0"
+approx = "0.5.1"

857: geo/geo bump  proj to 0.27.0 r=michaelkirk a=martinfrances107

The is a ongoing discussion in #856 about how to signal to the wider community that our dependencies are changing.

But this is issue follows the pattern developed in #850 



Co-authored-by: Martin <martinfrances107@hotmail.com>
@bors
Copy link
Contributor

bors bot commented Jun 24, 2022

Canceled.

@michaelkirk
Copy link
Member

bors retry

I pushed up a new commit to your branch to adapt to the latest proj.

@bors
Copy link
Contributor

bors bot commented Jun 24, 2022

Build succeeded:

@bors bors bot merged commit 6b01547 into georust:main Jun 24, 2022
@martinfrances107 martinfrances107 deleted the bump-proj branch December 21, 2023 08:40
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.

None yet

2 participants