Monorepo support

[tunnckoCore]

Currently, I'm not sure if it works, but basically it should be easy to support it, because we are based on git-semver-tags which understands Lerna tags.

[tunnckoCore]

Hm, actually we dont use it in the app. So we should make git-commits-since and/or git-semver-tags work without git, but with git log like string or array of commit message strings.

[tunnckoCore]

Use .listTags instead of getLatestRelease if pkg.workspaces and/or lerna.json is detected.

app/src/index.js

Lines 66 to 73 in 1a0f638

	const pkg = await getPkg(context, robot);
	if (!pkg) return null;
	const result = await context.github.repos.getLatestRelease(context.repo());
	const { data: commits } = await context.github.repos.getCommits(
	context.repo({ since: result.data.created_at }),
	);

ref: https://octokit.github.io/rest.js/#api-Repos-listTags

Use listTags, then .reduce over them to .getTag, so finally we'll have an array of tag objects which we should sort by tagger.date to be able to get the latest tag (no matter for which package it is), the important thing is that date, because than we'll pass it to .getCommits as { since: thatDate } option. After all that, we'll have all needed commits, and actually to the same thing which you'll do on the @tunnckocore/release-cli. Loop over all the commits, and for each of the packages inside each commit, call detectNextVersion. The final result, will be an array of Result objects which includes { increment, lastVersion, nextVersion, pkg, ... }

So for each item in that array, we'll call .createTag.

[tunnckoCore]

Needed changes in:

• detect-next-version
• parse-commit-message new plugin (New plugin for supporting monorepos tunnckoCoreLabs/parse-commit-message#56)
• recommended-bump
• @tunnckocore/release-cli (the future @standard-release/cli)

[tunnckoCore]

ref: Closing, based on conventional-commits/conventionalcommits.org#118 (comment)

Might not be needed. But out of curiosity, you can try to implement it as mentioned there - detect chore: release commits messages (or whatever regex is given on the config option) and get all the commits between those commits, which will then be passed to detect-next-version.

But in anyway, I don't think all this worth it and the time.

[tunnckoCore]

Also, latest comments on standard-release/cli#3