This PR adds support for outputting the semver version when bumping the buildpack. It utilizes the newly added semver output in jam (jam PR)
Technically this will break if used against an older version of jam. I could guard against that, but I'd rather use the broken builds as a forcing function to ensure that we keep jam up to date everywhere. This is similar to what we did when adding the --patch-only to this action - we expect it to run against a newer version of jam.
Turns out this won't break against an older version of jam - it will just emit an empty string for the semver bump. We can guard against this in the workflow (i.e. don't attempt to add a blank semver: label). We would probably want to do this anyway for safety.
This PR adds support for outputting the semver version when bumping the buildpack. It utilizes the newly added semver output in
jam(jam PR)Technically this will break if used against an older version ofjam. I could guard against that, but I'd rather use the broken builds as a forcing function to ensure that we keepjamup to date everywhere. This is similar to what we did when adding the--patch-onlyto this action - we expect it to run against a newer version ofjam.Turns out this won't break against an older version of
jam- it will just emit an empty string for the semver bump. We can guard against this in the workflow (i.e. don't attempt to add a blanksemver:label). We would probably want to do this anyway for safety.