Prepare for 6.0.2 release

[geerlingguy]

Working on the 6.0.2 release...

• Update CHANGELOG
• Cut a rug tag
• Add tag release notes

[geerlingguy]

The main fix here is #2100 — otherwise people may run into errors with new Drupal VM instances due to the prestissimo incompatibility.

[geerlingguy]

Done!

[yyss8]

Is there anyway to pin the composer version instead of installing composer 2 by default?
I'm seeing some conflicts like

  Problem 1
    - acquia/blt is locked to version 11.5.0 and an update of this package was not requested.
    - acquia/blt 11.5.0 requires composer-plugin-api ^1.1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.

after I updated to composer 2 outside the VM and I had to revert back to continue using composer 1 until those conflicts are addressed.

I'm not sure if I would see the same conflict errors when using composer 2 inside the VM but I think the Composer version should at least be the same outside or inside the VM.

nvm, I found that there is a config composer_version that I could use. Thanks