This PR ensures that the workflow that bumps buildpacks in the buildpack.toml file in a language family also adds semver:<value> labels to the PR, if possible.
This PR also bumps the version of jam used in the language family scripts so there should be no use-cases where the label is blank. But I'd rather be conservative and err on the side of successfully creating a PR with no label, rather than not creating a PR at all because the label doesn't exist.
⚠️ Note that this behavior will automatically label buildpacks with semver:majoreven if they are pre 1.0. This will result in automatic promotion to v1.0.0! ⚠️
This is probably fine - there's no reason not to bump to 1.0 for all the buildpacks we support with this CI - but I want to call it out explicitly.
This PR ensures that the workflow that bumps buildpacks in the
buildpack.toml
file in a language family also addssemver:<value>
labels to the PR, if possible.This PR also bumps the version of
jam
used in the language family scripts so there should be no use-cases where the label is blank. But I'd rather be conservative and err on the side of successfully creating a PR with no label, rather than not creating a PR at all because the label doesn't exist.⚠️ Note that this behavior will automatically label buildpacks with
semver:major
even if they are pre 1.0. This will result in automatic promotion to v1.0.0! ⚠️This is probably fine - there's no reason not to bump to 1.0 for all the buildpacks we support with this CI - but I want to call it out explicitly.