@@ -89,19 +89,24 @@ tools/dev/bun.sh tools/release/release-check.mjs
8989```
9090
9191For normal releases, leave the ` Release ` workflow's ` release_commit ` input
92- empty. If a publish or dry-run fails and a later ` main ` commit only fixes
93- release tooling, rerun ` Release ` from current ` main ` with ` release_commit ` set
94- to the full 40-character SHA that should be published. The workflow still runs
95- the latest release scripts, but it plans the release, selects CI artifacts,
96- checks product tags, and verifies publication against that selected release
97- commit. During ` publish ` , the workflow creates a temporary release-please target
98- branch at the selected commit so product tags and GitHub releases point at the
99- published source commit, then removes that temporary branch.
92+ empty. If release-please has already created product tags but a later publish
93+ step failed, rerun ` Release ` from current ` main ` ; ` publish ` keeps selecting the
94+ current-version product tags so the idempotent publish steps can complete
95+ missing assets and registry outputs. If a publish or dry-run fails and a later
96+ ` main ` commit only fixes release tooling, rerun ` Release ` from current ` main `
97+ with ` release_commit ` set to the full 40-character SHA that should be
98+ published. The workflow still runs the latest release scripts, but it plans the
99+ release, selects CI artifacts, checks product tags, and verifies publication
100+ against that selected release commit. During ` publish ` , the workflow creates a
101+ temporary release-please target branch at the selected commit so product tags
102+ and GitHub releases point at the published source commit, then removes that
103+ temporary branch.
100104
101105Do not use ` release_commit ` to skip CI for product source, version, changelog,
102106or release metadata changes. The workflow rejects lagging release commits unless
103107the intervening files are release tooling such as ` .github/workflows/ ` ,
104- ` .github/scripts/ ` , ` tools/release/ ` , ` tools/policy/ ` , or ` tools/xtask/ ` .
108+ ` .github/scripts/ ` , ` tools/dev/ ` , ` tools/release/ ` , ` tools/policy/ ` , or
109+ ` tools/xtask/ ` .
105110
106111## crates.io
107112
@@ -325,6 +330,9 @@ Setup:
325330 the repository. The release workflow creates two tags:
326331 - ` oliphaunt-swift-v<version> ` for the product release identity.
327332 - ` <version> ` for SwiftPM package resolution.
333+ Legacy pglite releases already use unscoped ` 0.1.0 ` through ` 0.5.1 ` tags, so
334+ the first Oliphaunt Swift release is bootstrapped from a ` 0.5.0 ` release-please
335+ baseline and minor-bumped by the introductory feature commits to ` 0.6.0 ` .
3283363 . Publish the compatible ` liboliphaunt-native-v<version> ` GitHub release assets
329337 before or during the same release plan. The Swift SDK pins that native core
330338 version in ` src/sdks/swift/LIBOLIPHAUNT_VERSION ` .
0 commit comments