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

Packagist not up to date #405

Closed
fleaz opened this issue May 19, 2022 · 5 comments · Fixed by #411
Closed

Packagist not up to date #405

fleaz opened this issue May 19, 2022 · 5 comments · Fixed by #411

Comments

@fleaz
Copy link

fleaz commented May 19, 2022

Description

Hey,

currently the latest two releases are missing on Packagist. The latest version on there is 4.0.0 but 4.0.1 and 4.0.2 are missing.

Could you please take a look whats broken? Because especially 4.0.2 is required for one of our customers to update to Craft 4

Best,
Felix

@rostockahoi
Copy link

In the meantime you can directly require the commit tagged with v4.0.2 with
composer require ether/seo:dev-v4-dev#9f563663e103bca1da02fb7f6cb48709ef6b674d

@dejury
Copy link
Contributor

dejury commented May 25, 2022

Any update(s) on this one?

@dejury
Copy link
Contributor

dejury commented Jun 3, 2022

Back again with an update on this issue. Found what the problem is, it is not related to packagist.

There is a versionnumber hardcoded in composer.json in the root of the project. This number is not updated in version 4.0.1 and 4.0.2.

I am not sure why this versionnumber is even there, I think it is better to remove this to prevent this issue in the future. Otherwise there should be a new release with the correct versionnumber inside the composer.json.

@rostockahoi
Copy link

Yes, the version number should be omitted in the composer file.

Tam added a commit that referenced this issue Jun 8, 2022
Fixing #405 & #406: Remove version number
@fleaz
Copy link
Author

fleaz commented Jun 8, 2022

Fixed in #411

@fleaz fleaz closed this as completed Jun 8, 2022
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 a pull request may close this issue.

3 participants