feat(preset): add codemirror group

[sachinraja]

Added as a pattern group because each package has a separate repository:
https://github.com/codemirror/view
https://github.com/codemirror/state
https://github.com/codemirror/lang-javascript

and so on.

[viceice]

I don't think this makes sense, as it's not a monorepo. They also have different releases.

[rarkins]

If they are released synchronously and must be updated together, then we use a monorepo group.
If they are not released synchronously but usually need to be updated at the same time and the Renovate community would benefit from this being done automatically then then can be put in group:recommended.

Otherwise if this is just an opinionated grouping/personal preference then it's best to configure it locally and not add it to Renovate.

[sachinraja]

They are not exactly released synchronously but a minor version bump will usually result in an update for all the other packages because they have hard dependencies on each other:

For example, if I install @codemirror/view and @codemirror/state, @codemirror/view has a dependency on @codemirror/state in the range ^0.19.2: https://github.com/codemirror/view/blob/c0be0ebe935ec6b821e5f92c087c208b9b8cdbfe/package.json#L30. If @codemirror/state gets a minor version bump to ^0.2.0 and @codemirror/view gets a minor version bump to ^0.2.0 to update it and I only update @codemirror/view, then deduping cannot happen. Ending up with two versions of it will likely cause problems. That being said, I'm not sure if it is planned to independently version them or if they are just updating because of the hard dependencies. I could ask if necessary.

So I'm not sure if this should be put in the monorepo group or group:recommended.

[viceice]

This is not a mono repo and the updates don't need to be grouped. dedupe is not a issue for renovate here.

So i think this should be done per use case and not by default in any renovate preset.

[sachinraja]

The app can break if the dependencies are not updated together though because deduping is actually necessary sometimes, for example, see codemirror/dev#503 (comment).

[rarkins]

@viceice sounds like they've had enough problems that we could group by default. I'd go with group:recommended

[viceice]

ok, so @sachinraja please apply the grouping to group:recommended

like this

renovate/lib/config/presets/internal/group.ts

Lines 451 to 462 in 050b6a9

	jekyllEcosystem: {
	description: 'Group jekyll and related ruby packages together',
	packageRules: [
	{
	matchSourceUrlPrefixes: [
	'https://github.com/jekyll/',
	'https://github.com/github/pages-gem',
	],
	groupName: 'jekyll ecosystem packages',
	},
	],
	},

renovate/lib/config/presets/internal/group.ts

Line 62 in 050b6a9

'group:jekyllEcosystem',

[renovate-release]

🎉 This PR is included in version 27.9.0 🎉

The release is available on:

• GitHub release
• 27.9.0

Your semantic-release bot 📦🚀