Skip to content

Correctly specify minimum dependency versions#185

Merged
bradleybeddoes merged 3 commits into0.2-maintfrom
dependency-versions
Mar 18, 2018
Merged

Correctly specify minimum dependency versions#185
bradleybeddoes merged 3 commits into0.2-maintfrom
dependency-versions

Conversation

@smangelsdorf
Copy link
Contributor

There are cases where Gotham (and by extension, Gotham apps) won't build correctly with the currently specified minimum version. Specifying the minimum version which permits Gotham to build correctly ensures that it can't be broken by apps with old Cargo.lock files.

Fixes #180

This also brings the Travis CI changes from #173 and #174 into the 0.2-maint branch.

smangelsdorf and others added 3 commits March 16, 2018 17:58
There are cases where gotham (and by extension, gotham apps) won't build
correctly with the currently specified minimum version. Specifying the
minimum version which permits gotham to build correctly ensures that it
can't be broken by apps with old `Cargo.lock` files.

Fixes #180
Right now, 3 shards separately spend ~10 minutes building a release
version of rustfmt from source so that they can perform the same <1s
check over the same source code.

Instead, one shard will compile and run rustfmt, while the other 3 will
just run the tests.

rustfmt passing with a stable `cargo` version should be sufficient.

This should speed up travis, perform less redundant work, and make test
shards less likely to timeout.
This regresses us to a more official release (0.3.8 rather than 0.4.0)
but saves 8~10 minutes of compiling rustfmt from scratch.
log = "0.4"
hyper = { version = "0.11", features = [] }
log = "0.4.1"
hyper = { version = "0.11.7", features = [] }
Copy link
Contributor

Choose a reason for hiding this comment

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

epic nit, ignorable.

Given we're not using any hyper features should we take the opportunity to revert back to hyper = "0.11.7" format?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought the goal here was to explicitly opt out of hyper's default features. From looking at the latest hyper, that seems to opt us out of tokio-proto compatibility (since we don't need it). I might be misreading though.

Copy link
Contributor

Choose a reason for hiding this comment

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

👍 carrying on.

@bradleybeddoes bradleybeddoes merged commit 1136f5e into 0.2-maint Mar 18, 2018
@bradleybeddoes bradleybeddoes deleted the dependency-versions branch March 18, 2018 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants