Composer stability fix to get Drupal 9.3.x. #218
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this Pull Request do?
Set composer default options to opt for stable versions by default.
What's new?
The playbook was using geerlingguy.composer's default composer tags which included prefer-dist, this was causing composer create-project to get the development version of drupal/recommended-project.
We just needed to explicitly specify Flysystem as a beta since it has no stable release.
(i.e. Regeneration activity, etc.)?
No, existing drupal installs aren't replaced by the playbook.
How should this be tested?
Run a fresh playbook install.
Verify that the version of Drupal core is 9.3.x (as of June 8 2022).
Verify derivative creation.
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora-Devops/committers