-
Notifications
You must be signed in to change notification settings - Fork 393
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
composer install is behind the releases branch #660
Comments
Packagist lists v3.0.7 as the latest version: https://packagist.org/packages/humanmade/s3-uploads, could this be a caching issue at your end? What does your final |
Not getting any errors specifically stating 3.0.7, getting usual error [requirements could not be resolved] when stating 3.0.8 as version required. 3.0.7 no errors. version showed inside Wordpress 3.0.3 Reason to upgrade is to stop the failure to upload images locally when developing locally - folders all created just no file. Tried on three browsers, no cache running locally, all history and cache deleted from browsers and still showing version 3.0.3. Perplexed... |
"require": { |
Check |
composer why humanmade/s3-uploads |
Oh, when you say "installs v3.0.3" do you mean that the version specifically on the plugins page in the WordPress admin displays 3.0.3? If so, yes, this was an issue where the version there was not manually bumped: #624 |
Bingo - exactly this... |
When running composer require humanmade/s3-uploads this installs v3.0.3 but the releases are at 3.0.7.
This is causing some issues specifically local dev, just wondered when they will be sync'd or should we pull from a different branch now and not master?
The text was updated successfully, but these errors were encountered: