fix(release): restore clean publish path#89
Merged
Conversation
fdddb7c to
f213560
Compare
f213560 to
d6e976f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
oliphaunt-swiftfrom the legacy-safe0.5.0baseline so the release PR creates the first SwiftPM package tag at0.6.00.6.0after the bootstrap baselineValidation
tools/dev/bun.sh tools/release/check_release_please_config.mjstools/dev/bun.sh tools/release/sync-release-pr.mjs --checktools/dev/bun.sh tools/release/release-check.mjstools/dev/bun.sh tools/release/release_plan.mjs --from-product-tags --include-current-tags --head-ref HEAD --format jsonRelease path after merge
Run the Release workflow from
mainwithprepare-release-pr, merge the generated release PR, then runpublishfrommainwith an emptyrelease_commit. The Swift entry in the generated release PR should be0.6.0; other first Oliphaunt product entries should remain on their normal first product versions.