Open bryanpizzillo opened 6 days ago
1308152 : Add stream wrappers to access extension files (https://www.drupal.org/files/issues/2021-12-15/1308152-395.patch)
https://www.drupal.org/files/issues/2024-06-24/1308152.patch
"2971390 : Make exposure of translation meta fields conditional" : "https://www.drupal.org/files/issues/2023-08-25/2971390-75.patch",
composer cgov-clean && composer install
blt cgov:reinstall --no-interaction && npm ci && npm run build:prod
drush features:list:packages
composer require 'drupal/features:^3.14'
drush updb
drush features:list:packages
1308152
- Changed to https://www.drupal.org/files/issues/2024-06-24/1308152.patch
2971390
-- ?????????composer require 'drupal/samlauth:^3.10'
composer require drupal/core-composer-scaffold:~10.3.8 drupal/core-recommended:~10.3.8 --update-with-dependencies --no-update
composer require drupal/core-dev:~10.3.8 --dev --update-with-dependencies --no-update
composer update
tbachert/spi
- I answered no. See https://www.drupal.org/project/drupal/issues/3478895#comment-15838963
This is probably going to be 10.3.x as Drupal 10.4.x won't be out until mid-Dec. This should follow the steps in Updating Drupal Core.
Additional Tasks
warning of undefined array key "yes"
message we always see.drush updb
. Then you should run the pre-upgrade tasks. The reason is that the update of features could trigger some differences in packages.drupal/samlauth
from "dev-3.x#0c12729843c32e865ce2d81d3dff2e8b0a9f7b17"to
3.10.
3.10` contains the commit from the dev branch, but a composer update is gonna pull in the latest dev commit instead of a latest stable version.