[Neos] How to upgrade to beta?

[Christian Müller]

Hi Jigal,

the easiest approach is the following: Update your base distribution 
composer.json (either by getting it from git or by hand) to require the 
beta versions of packages. Delete all Flow/Neos packages from 
Packages/Framework and Packages/Application, remove composer.lock and 
run composer install. That should bring you to a working version.

Our version tagging in the packages is not yet ideal I think, we 
probably need to work on that some more to make this kind of upgrade 
easier. But with the amount of changes currently going on we pin 
packages to specific betas of other packages otherwise the installation 
would not work.

Cheers,
Christian

Jigal van Hemert 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
>