Specific Versions in gemfile about uri_signer HOT 5 CLOSED

Yes, pessimistic versioning is best.

from uri_signer.

With the Pessimistic Operator we still will have a problem.

Rack:

You have requested:
  rack ~> 1.1.6

The bundle currently has rack locked at 1.5.2.
Try running `bundle update rack`

Addressable

You have requested:
  addressable = 2.2.7

The bundle currently has addressable locked at 2.3.5.
Try running `bundle update addressable`

Km-legacy is stuck in the dark ages, while the api will be running new stuff.

from uri_signer.

Yeah, you'll need to do ~> 1.1 and ~> 2.3.

from uri_signer.

Removing all the versions and going to push a 0.1.0 build. I don't want to make this a 1.0.0 until we remove all external dependencies.

I would normally be for pessimistic versioning, however, we use this in a legacy code base that can't use newer versions, so updating this and making sure it can be used with newer software doesn't seem possible.

from uri_signer.

Closed in version 0.1.0

from uri_signer.