Can't update Kirby 3 via Composer anymore

I have installed Kirby using Composer. Right now my Kirby installation is at v 3.1.3 and I want to update to the latest (at the moment v 3.2.3) if I cd to the root folder using my Terminal and run

composer update getkirby/cms

I get:

Nothing to install or update
Writing lock file
Generating optimized autoload files

My composer.json looks like this:

{
  "minimum-stability": "dev",
  "prefer-stable": true,
  "name": "getkirby/plainkit",
  "description": "Kirby Plainkit",
  "type": "project",
  "keywords": [
    "kirby",
    "cms",
    "starterkit"
  ],
  "homepage": "https://getkirby.com",
  "authors": [
    {
      "name": "Bastian Allgeier",
      "email": "bastian@getkirby.com",
      "homepage": "https://getkirby.com"
    }
  ],
  "support": {
    "email": "support@getkirby.com",
    "issues": "https://github.com/getkirby/starterkit/issues",
    "forum": "https://forum.getkirby.com",
    "source": "https://github.com/getkirby/starterkit"
  },
  "require": {
    "php": ">=7.1.0",
    "getkirby/cms": "^3.0",
    "elasticsearch/elasticsearch": "~6.0",
    "aws/aws-sdk-php": "^3.80",
    "k-community/markdown-field": "^1.0",
    "sylvainjule/pagetable": "^1.0"
  },
  "config": {
    "optimize-autoloader": true
  }
}

Anyone else having this problem?

Try bumping the version number up in the composer.json file and running composer install again.

"getkirby/cms": "^3.2",

Works fine now. Didn’t know I needed to change that until version went to 4.
Thanks

I wouldn’t have expected this to be necessary, either.

next time try deleting

  1. composer.lock file
  2. vendor folder

changing the version in composer.json is not necessary.

upgrading your global composer installation might be a good idea as well. but should not really affect this issue.

2 Likes