-
Notifications
You must be signed in to change notification settings - Fork 74
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
Upload to packagist.org a new version of components/ember #64
Comments
We are publishing tagged builds to the referenced repo (https://github.com/components/ember) for each release. |
Apparently, somathing wrong with packagist: I submitted my own fork to packagist See |
|
Can you add new releases for the package ? I also use the package components/ember-data and it requires ember version 1.* . Because of the requirement, I can't use the master release or any new releases like versio 1.8. The last release you added was 1.4.0-beta.3. Can you add more releases or remove the requirement? |
You need to add a comma in composer.json between the versions for all failing tags Skipped tag 1.9.0-beta.1, Invalid package information: => must be ">=1.7.0, <= 2.1.0" instead of " >=1.7.0 <= 2.1.0" |
Deleting the |
@RobLoach - We have users ACTIVELY using the |
@rwjblue Ah, sorry about that. Do you know which tag |
@RobLoach - It is auto-published (by Travis) from the stable branch of emberjs/ember.js. I can update the composer.json there and trigger a Travis run to republish. |
composer.json $ composer update error -> Could not load package components/ember in http://packagist.org: [UnexpectedValueException] Could not parse version constraint >=1.7 < 2.1: Invalid version string "1.7 < 2.1" |
@brunogoossens, composer version parsing behaviour has been changed so that |
https://packagist.org/packages/components/ember version is still 1.4
The text was updated successfully, but these errors were encountered: