periodic maintenance. Bump version of approx from 0.4.0 to 0.51 #849
Comments
martinfrances107
added a commit
to martinfrances107/geo
that referenced
this issue
Jun 18, 2022
martinfrances107
added a commit
to martinfrances107/geo
that referenced
this issue
Jun 21, 2022
martinfrances107
added a commit
to martinfrances107/geo
that referenced
this issue
Jun 23, 2022
bors bot
added a commit
that referenced
this issue
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 bot
added a commit
that referenced
this issue
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 bot
added a commit
that referenced
this issue
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> Co-authored-by: Michael Kirk <michael.code@endoftheworl.de>
|
Fixed in #850 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know this is a contraversial topic, so I am going to tread lightly, because I know other have different perspectives. I am raising this as an issue just to I can get a sense of maintainers and other contributors views.
I am a minor contributer here, but I also have a project that relies on this project, so I going to start off speaking as maintainer of a upstream project.
Upstream: I periodically run cargo-outdated, for secuirty and so I can de-risk the techinical debt of a subpackage making radical changes to the API on me.
With a complex set of sub-dependancies 'Cargo outdated' generates a lot of information which has to be reasonded with and then filtered out.
I am seeing that if I can bump the version of approx as stated in the title. then it would quell the noise from cargo outdated.
I am about to submit a PR with the changes to all the Cargo.toml filles bumping the minor version number
There are other subpackages that are slowly getting outdated. Depending on how to community feels ... I will submit PR to slowly bring everything upto date.
The text was updated successfully, but these errors were encountered: