Skip to content

Remove upper bounds on versions of cereal and crypto-api#14

Closed
larskuhtz wants to merge 1 commit intometeficha:masterfrom
alephcloud:master
Closed

Remove upper bounds on versions of cereal and crypto-api#14
larskuhtz wants to merge 1 commit intometeficha:masterfrom
alephcloud:master

Conversation

@larskuhtz
Copy link
Copy Markdown

The upper bounds for cereal and crypto-api do exclude the most recent versions of these packages. After removing the bounds the package still builds and works for me. I haven't done any specific tests. I guess that serialization with the new version of cereal is backward compatible but I haven't checked.

@kazu-yamamoto
Copy link
Copy Markdown

I also wish that a new version including this patch will be released soon.

@vincenthz
Copy link
Copy Markdown

Just got bitten by this too, @meteficha please remove the upper bounds.

@AaronFriel
Copy link
Copy Markdown

Seconded. Please increase upper bounds to allow anything up to the next major version, at least. i.e.: 1.0 for 0.x dependencies.

@meteficha
Copy link
Copy Markdown
Owner

Hey, guys! Sorry I've been MIA for a few months. It seems to me that @snoyberg fixed the current problems by just bumping the version constraints, so does anybody still has any problems with skein-1.0.8.1?

In general, I don't like removing upper bounds, especially for crypto-api which has seen quite a few breaking changes without ever reaching 1.0. Usually I'm responsive enough to bump the constraints before creating too much hassles, but I've clearly failed this time. Still, I'm not sure if dropping the upper bounds is the best course of action.

If anybody has any comments to share about this, I'm all ears. And again, sorry for not taking care of skein.

@meteficha
Copy link
Copy Markdown
Owner

Well, closing this issue then. :)

@meteficha meteficha closed this Apr 3, 2014
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.

5 participants