[Neos] How to upgrade to beta?

[Aske Ertmann]

Hi Jigal

Actually you’re on a good track, you just need to set the minimum-stability to be able to require non stable versions.

I can’t find any composer command for setting it after initialising a project, but in your composer.json set "minimum-stability": “dev” on the first level. Could also be set to “beta”.

I updated a project today just by changing the versions from 1.0.* to 1.1.* and setting the minimum-stability flag. When the 1.1 is officially released the flag won’t be necessary of course.

Another way of doing this would be to require 1.1.*@beta.

It shouldn’t be necessary to rely on any composer.lock from the base distribution.

Hope it helps and sorry for the slow response.

Best regards
Aske

On 28 May 2014, at 07:32, Jigal van Hemert <jigal.van.hemert at typo3.org> wrote:

> Hi,
> 
> On 27-5-2014 18:35, Marcin Ryzycki wrote:
>> You can checkout to 1.1 branch [1] which for now always contains
>> most-recent 1.1 released version (currently 1.1.0-beta3) or to specific
>> tag (again, 1.1.0-beta3). Using dev-master might be sometimes bumpy road ;)
>> 
>> git checkout tags/1.1.0-beta3
> 
> Won't work with the installation made with composer as there is not git clone included. I have no idea what the effects are of cloning a repo inside a directory with an existing installation...
> 
> There is a page about upgrading existing installations [1] which says "you can update an existing installation to the a specific version, without having to create a new project", but the commands in the example:
> cd /installation-root/
> composer require "typo3/neos:1.0.*"
> composer require "typo3/neos-nodetypes:1.0.*"
> composer require "typo3/neosdemotypo3org:1.0.*"
> composer require "typo3/neos-kickstarter:1.0.*"
> # Remember to flush the caches afterwards
> ./flow flow:cache:flush --force
> ./flow doctrine:migrate
> 
> won't work with a beta version:
> --------------------------------------------------------------
> $ composer require "typo3/neos:1.1.0-beta3"
> ./composer.json has been updated
> Loading composer repositories with package information
> Updating dependencies (including require-dev)
> Your requirements could not be resolved to an installable set of packages.
> 
>  Problem 1
>    - Installation request for typo3/neos 1.1.0-beta3 -> satisfiable by typo3/neos[1.1.0-beta3].
>    - typo3/neos 1.1.0-beta3 requires typo3/flow 2.2.* -> no matching package found.
>  Problem 2
>    - typo3/neos-nodetypes 1.0.2 requires typo3/neos 1.0.* -> no matching package found.
>    - typo3/neos-nodetypes 1.0.2 requires typo3/neos 1.0.* -> no matching package found.
>    - Installation request for typo3/neos-nodetypes == 1.0.2.0 -> satisfiable by typo3/neos-nodetypes[1.0.2].
> 
> Potential causes:
> - A typo in the package name
> - The package is not available in a stable-enough version according to your minimum-stability setting
>   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.
> 
> Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
> 
> Installation failed, reverting ./composer.json to its original content.
> --------------------------------------------------------------
> 
> Anyone?
> 
> [1] http://neos.typo3.org/download/upgrade-instructions.html
> 
> -- 
> Jigal van Hemert
> TYPO3 CMS Active Contributor
> 
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos