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

Use Semver::satisfies with a try catch #42

Merged
merged 1 commit into from
Apr 26, 2016

Conversation

soullivaneuh
Copy link
Owner

Fixes #40.

@Seldaek Could you please have a quick look to tell me if my approach is good? Thanks.

`'@package_version@' === Composer::VERSION` condition is not enough.

On composer snapshots, the full commit is given on this constant,
throwing unexpected value exceptions.

See: composer/composer#5028 (comment)

With this method, we are sure that any fail of Semver::satisfies will be properly handled.
@soullivaneuh
Copy link
Owner Author

soullivaneuh commented Apr 26, 2016

If you are already on v2.0.0, here is the way to upgrade to v2.0.1 and get rid of the issue:

$ composer global update --no-plugins
Changed current directory to /home/sullivan/.composer
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Removing sllh/composer-versions-check (v2.0.0)
  - Installing sllh/composer-versions-check (v2.0.1)
    Downloading: 100%         

Writing lock file
Generating autoload files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant