Closed LarkRiseMedia closed 8 months ago
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 composer.json
look like? Have you tried explicitly requiring 3.0.7 or higher when declaring the dependency? That way if there is an issue that prevents newer versions than 3.0.3 being used composer will tell you
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": { "php": ">=8.0", "composer/installers": "^2.2", "vlucas/phpdotenv": "^5.5", "oscarotero/env": "^2.1", "roots/bedrock-autoloader": "^1.0", "roots/bedrock-disallow-indexing": "^2.0", "roots/wordpress": "6.4.2", "roots/wp-config": "1.0.0", "roots/wp-password-bcrypt": "1.1.0", "wpackagist-theme/twentytwentyfour": "^1.0", "humanmade/s3-uploads": "3.0.7", "wpackagist-plugin/regenerate-thumbnails":"^3.1.6"
Check composer why humanmade/s3-uploads
and see if it tells you anything else interesting about the version
composer why humanmade/s3-uploads roots/bedrock - requires humanmade/s3-uploads (3.0.7)
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: https://github.com/humanmade/S3-Uploads/pull/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?