xjm

This will need to be fixed in both `tag.sh` and `sec.sh`, once the handbook for the official release process is updated. https://www.drupal.org/core/maintainers/create-core-release The script only automates the official process. Edit:...

Every time we've set `COMPOSER_ROOT_VERSION` it's broken the release process. It's been added twice to the script and then removed twice because it prevented both 8.8.0-beta1 and 8.8.0-rc1 from being...

Scenarios that should be manually tested (locally, obviously) if we change the process and scripts: - 8.9.0-beta1 - 8.9.0-rc1 - 8.9.0 - 8.8.1 as a patch release - 8.8.1 as...

Also branching 8.1.0x and 9.1.x.

I tried implementing the recommended changes. Resulted in "Your requirements could not be resolved to an installable set of packages." Full output: ```$ ../core_release/tag.sh Enter the D8 release number (e.g....

Sorry, meant to supply the diff also: ```diff --git a/tag.sh b/tag.sh index 7c3de99..677ca6d 100755 --- a/tag.sh +++ b/tag.sh @@ -55,6 +55,7 @@ echo "Updating metapackage versions to ${v} and tagging."...

#11 resolved this for the normal release tagging script. We still need to amend the security release script, verify whether the branching script needs any changes, and then update all...

I tried a similar strategy to #11 for `sec.sh`, but there's a couple reasons that won't actually give the correct result. Since we're merging changes from a different branch, the...

```diff --git a/sec.sh b/sec.sh index bac852d..a448bcc 100755 --- a/sec.sh +++ b/sec.sh @@ -267,8 +267,8 @@ for i in "${!versions[@]}"; do git add CHANGELOG.txt # D8 and higher need to have...

In the interim, just do https://github.com/ericduran/drupalcores/pull/82 ?