Needs a way to distinguish breaking changes of stable modules and unstable modules in the release note about deno_std

[babiabeo]

How about adding stable and unstable labels? I think actions/labeler can add them automatically based on the changed module.

[iuioiua]

Yep, that sounds fine to me.

[kt3k]

Ok. Let's try this pattern for a while

[unstable] BREAKING(semver): remove Foo API

[iuioiua]

I suggest BREAKING(unstable) for unstable breaking changes and BREAKING(stable) for stable.

[kt3k]

How about adding stable and unstable labels? I think actions/labeler can add them automatically based on the changed module.

Sounds a good idea for indicating PRs unstable/stable

@iuioiua

I suggest BREAKING(unstable) for unstable breaking changes and BREAKING(stable) for stable.

This makes sense as CLI repo does feat(unstable) etc. Can we somehow also specify the affected module names?

[iuioiua]

Actually, how's [unstable | stable] BREAKING(<scope>)? Perhaps we should stick to having the scope contained within the round brackets.

[kt3k]

So the actual commit message would look like: [unstable] BREAKING(semver): remove Foo API?

This looks good to me, but I'd prefer to omit [stable] if it's from stable module.