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

Plans for a new version? #140

Closed
deivid-rodriguez opened this issue Jun 2, 2020 · 17 comments
Closed

Plans for a new version? #140

deivid-rodriguez opened this issue Jun 2, 2020 · 17 comments

Comments

@deivid-rodriguez
Copy link
Contributor

Hi!

I upgraded both rubygems & bundler to use the latest and greatest revision of Molinillo:

I was wondering if there are any plans to release the latest changes in the master branch of Molinillo, so we can ship both libraries with Molinillo's code that matches an actual release.

@deivid-rodriguez
Copy link
Contributor Author

Ping.

@segiddins
Copy link
Member

A new version should be released the next time a CocoaPods release happens

@deivid-rodriguez
Copy link
Contributor Author

Nice, thanks a lot!

I'm watching releases now on https://github.com/CocoaPods/CocoaPods :)

@deivid-rodriguez
Copy link
Contributor Author

Hi @segiddins! A CocoaPods release happened. Should I expect a new Molinillo release now?

@segiddins
Copy link
Member

Cc @dnkoutso did you skip gems during the release?

@dnkoutso
Copy link
Contributor

heh. rainforest does a shallow clone as its initial sync and molinillo did not show up as a gem with new commits. Looking to release today.

@dnkoutso
Copy link
Contributor

Looks like i cant ship 0.7.0 due to a spec failure:

Failures:

  1) Molinillo::Resolver in general raises conflicts with requirement trees
     Failure/Error:
               expect { test_case.resolve(index_class) }.to raise_error(VersionConflict) do |conflict|
                 expect(conflict.message).to eq <<-EOS.strip
       Unable to satisfy the following requirements:
       
       - `json (>= 1.7.7)` required by `berkshelf (2.0.7)`
       - `json (<= 1.7.7, >= 1.4.4)` required by `chef (10.26)`
                 EOS
                 expect(conflict.message_with_trees(:version_for_spec => lambda(&:version))).to eq <<-EOS.strip
       Molinillo could not find compatible versions for possibility named "json":
         In user-specified dependency:
     
       expected: "Unable to satisfy the following requirements:\n\n- `json (>= 1.7.7)` required by `berkshelf (2.0.7)`\n- `json (<= 1.7.7, >= 1.4.4)` required by `chef (10.26)`"
            got: "Unable to satisfy the following requirements:\n\n- `json (>= 1.7.7)` required by `berkshelf (2.0.7)`\n- `json (>= 1.4.4, <= 1.7.7)` required by `chef (10.26)`"
     
       (compared using ==)
     
       Diff:
       @@ -1,5 +1,5 @@
        Unable to satisfy the following requirements:
        
        - `json (>= 1.7.7)` required by `berkshelf (2.0.7)`
       -- `json (<= 1.7.7, >= 1.4.4)` required by `chef (10.26)`
       +- `json (>= 1.4.4, <= 1.7.7)` required by `chef (10.26)`
       
     # ./spec/resolver_spec.rb:180:in `block (3 levels) in <module:Molinillo>'

Finished in 2.48 seconds (files took 0.21279 seconds to load)
260 examples, 1 failure, 1 pending

@dnkoutso
Copy link
Contributor

Not sure if this is a simple update to the spec or something else has changed.

@deivid-rodriguez
Copy link
Contributor Author

@dnkoutso I think d42b00a should help!

@dnkoutso
Copy link
Contributor

@deivid-rodriguez that commit seems like its changing the order which is causing the spec failure?

@deivid-rodriguez
Copy link
Contributor Author

Essentially the order of that spec expectations depends on the rubygems version being used by the tests. The current ordering works for rubygems versions lower than 2.7.8 or rubygems versions higher than 3.1.2. If you're using a rubygems version in between it won't work. If we want specs to support those intermediate versions, we'd need to conditionally change the expectation according to the rubygems version being run.

@dnkoutso
Copy link
Contributor

@deivid-rodriguez ah thanks! I missed that part. Trying now.

@dnkoutso
Copy link
Contributor

Shipped! https://github.com/CocoaPods/molinillo/releases/0.7.0

@deivid-rodriguez I am not sure if you can use it though immediately..............at least not with CocoaPods because it is locked with 0.6.6 https://github.com/CocoaPods/CocoaPods/blob/master/cocoapods.gemspec#L39

I need to make one more release of cp 1.10.1 for you to be able to use it and change this requirement

@dnkoutso
Copy link
Contributor

Going to close this now since 0.7.0 shipped. Will update cocoapods separately.

@dnkoutso
Copy link
Contributor

CP Bump PR CocoaPods/CocoaPods#10164

@deivid-rodriguez
Copy link
Contributor Author

Actually my request was not due to wanting to use the latest Molinillo code with cocoapods, but to get some fixes I added released, so that the code of molinillo that we vendor inside bundler & rubygems matches a released version of molinillo.

Anyways, thanks a lot @dnkoutso for the release! 🎉

@dnkoutso
Copy link
Contributor

nice!

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

No branches or pull requests

3 participants