Resolves:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/core-dev[9.2.0-alpha1, ..., 9.2.x-dev] require symfony/finder ^4.4 -> found symfony/finder[v4.4.0-BETA1, ..., 4.4.x-dev] but the package is fixed to v5.3.7 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires drupal/core-dev ~9.2.0 -> satisfiable by drupal/core-dev[9.2.0-alpha1, ..., 9.2.x-dev].
This enables more of the dependencies and configuration that need to be
present in the root project composer.json to be managed in the farmOS
repository itself, including drupal/core-composer-scaffold and
drupal/core-dev, which should match the drupal/core version defined in
the farmOS composer.json.
Previously these were declared in the project composer.json template
in https://github.com/farmOS/composer-project. This configuraton is
used as a template when a new farmOS project is created via
`composer create-project farmos/project`, but after initial setup it
is maintained by the end user. This means that updates to the project
composer.json generally requires the end-user to make changes
manually. This would be required every time farmOS requires a minor
version update of Drupal core.
So instead, we can manage those update in this new composer.project.json,
and use wikimedia/composer-merge-plugin to merge that into the project
composer.json. This allows the project composer.json to be much simpler,
and therefore will require less frequent manual updates.
**Why?** Fix some weird behavior and make sure
inconsistent states cannot occur;
* Allow setting the archived timestamp at the same
time as moving a plan to the archived state.
* Ensure that the archived timestamp cannot be set
without also transitioning into the archived state.
* Ensure that the arhived timestamp cannot be set to
NULL without transitioning back to the active state.
**Why?** Fix some weird behavior and make sure
inconsistent states cannot occur;
* Allow setting the archived timestamp at the same
time as moving an asset to the archived state.
* Ensure that the archived timestamp cannot be set
without also transitioning into the archived state.
* Ensure that the arhived timestamp cannot be set to
NULL without transitioning back to the active state.
**Why?** The docs were out of date - not capturing the
need for a Chrome/Selenium container and including info
about an XDebug work-around that isn't needed any more.
Michael Stenta
paul121
Symbioquine
Eva Martinez