Update composer-merge-plugin to latest version

Ah great!

The 1.3.0 release of merge plugin was just tagged, guessing that affects this patch?

Still good.

I am mainly rerolling here, but I made a small change to composer.json and I'd like for someone to review it. It essentially means the same but IMO, gives a clearer meaning.

diff --git a/composer.json b/composer.json
index 04e1806..7f170ce 100644
--- a/composer.json
+++ b/composer.json
@@ -5,7 +5,7 @@
   "license": "GPL-2.0+",
   "require": {
     "composer/installers": "^1.0.21",
-    "wikimedia/composer-merge-plugin": "^1.3.0"
+    "wikimedia/composer-merge-plugin": "~1.3"
   },
   "replace": {
     "drupal/core": "~8.0"

Just FYI, the reroll conflict was probably because of #2609110: Update Twig to 1.23.1.

+++ b/composer.json
@@ -5,7 +5,7 @@
-    "wikimedia/composer-merge-plugin": "^1.3.0"
+    "wikimedia/composer-merge-plugin": "~1.3"

According https://getcomposer.org/doc/articles/versions.md#caret
"allow non-breaking updates"
so this change allows 1.* without checking compatibility... not sure that right

@andypost: Re #16. If you interpret the versions correctly, ^1.3.0 is identical to ~1.3. This is what they translate to:

^1.3.0 => ">=1.3.0, <2.0"
~1.3 => ">=1.3, <2.0"

"allow non-breaking updates"

That is if the project follows semantic versioning (which many do). Both constraints will allow 1.* from 1.3 onwards. As per semantic versioning, there shouldn't be any breaking changes in 1.* at all, which means both constraints should not break. If there happens to be a breaking change down the line (unlikely), we would have to constraint the version in both cases.

So, why change? This discussion is actually the proof why. Many are confused by the caret operator and that is why it is better to switch it to the more readable representation if possible. See Twig's version constraint for example. ^1.23.1 translates to ">=1.23.1, <2.0" whereas ~1.23.1 would translate to ">=1.23.1, <1.24". They are quite different.

I hope this helps understand the caret operator and why "~1.3" is identical to "^1.3.0".

@hussainweb thanx for explanation!
that works

+1 on the RTBC as it stands. But it would also be nice to use the new require section for core/composer.json.

Committed 7485eaa and pushed to 8.0.x. Thanks!

@Mile23 I don;t think this should go in core/composer.json because I think it needs to be in the root composer.json as this is how merging actually works

I meant: Currently the root composer.json file has extra.include.core/composer.json. It *could* have extra.require.core/composer.json, which would error out if that file isn't present.

No worries though.