Skip to content

ci: add a Tag release workflow that bumps and pushes the release tag - #51

Merged
mosherBT merged 7 commits into
masterfrom
brennanmosher/ide-86-sdk-release-process-improvement
Nov 11, 2026
Merged

mosherBT merged 7 commits into
masterfrom
brennanmosher/ide-86-sdk-release-process-improvement

Conversation

@mosherBT

@mosherBT mosherBT commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Why

IDE-86. Releasing means tagging by hand; this makes it a dispatch, and the version the SDK reports has drifted from the release (v1.1.0 and v1.2.0 both report 1.0.0).

What Changed

  • CI: new tag.yml — workflow_dispatch with a minor (default) / major / patch bump. Refuses non-master refs, derives the next version from the latest release tag, pushes vX.Y.Z, calls CI, then publishes a GitHub release with generated notes once CI passes.
  • CI: android-sdk-ci.yml gains workflow_call, since a tag pushed with GITHUB_TOKEN doesn't trigger it.
  • Behaviour change — android_sdk: the SDK version now comes from the release tag. On JitPack builds, versionName and BuildConfig.VERSION_NAME (sent as osdk) are the tag minus its v, so v1.3.0 reports android-1.3.0-…. optableVersionName in gradle.properties is only used for local and CI builds and no longer needs bumping for a release.

Comment thread .github/workflows/tag.yml Resolved
Comment thread .github/workflows/tag.yml Resolved

@jrosendahl-opt jrosendahl-opt left a comment

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.

LGTM

@mosherBT
mosherBT merged commit f156d3d into master Nov 11, 2026
3 checks passed
@mosherBT
mosherBT deleted the brennanmosher/ide-86-sdk-release-process-improvement branch November 11, 2026 22:01
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