Skip to content

Publish releases automatically on version-bump merges to trunk#1363

Open
crazytonyli wants to merge 2 commits into
trunkfrom
add/auto-detect-swift-release
Open

Publish releases automatically on version-bump merges to trunk#1363
crazytonyli wants to merge 2 commits into
trunkfrom
add/auto-detect-swift-release

Conversation

@crazytonyli
Copy link
Copy Markdown
Contributor

@crazytonyli crazytonyli commented May 29, 2026

A new Detect release step inspects each trunk build's CHANGELOG.md change and, when the commit added a new version header that is not yet tagged, uploads a step that builds and publishes the release. This removes the manual Buildkite trigger from the normal flow, while NEW_VERSION is kept as a manual override for recovery or forcing a release.

Please note: manually starting a new build with NEW_VERSION is still available. But it should be treated as a fallback now.

A new Detect release step inspects each trunk build's CHANGELOG.md change and, when the commit added a new version header that is not yet tagged, uploads a step that builds and publishes the release. This removes the manual Buildkite trigger from the normal flow, while NEW_VERSION is kept as a manual override for recovery or forcing a release.
@crazytonyli crazytonyli requested review from jkmassel and oguzkocer May 29, 2026 02:58
@wpmobilebot
Copy link
Copy Markdown
Collaborator

XCFramework Build

This PR's XCFramework is available for testing. Add to your Package.swift:

.package(url: "https://github.com/automattic/wordpress-rs", branch: "pr-build/1363")

Built from 4c69735

}

if [ -n "${NEW_VERSION:-}" ]; then
version="$NEW_VERSION"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably run a semver check just in case NEW_VERSION is not in our expected format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants