Skip to content

release: denote AOSP source ref in release title + notes#2

Merged
Jawnnypoo merged 1 commit into
mainfrom
release-notes-source-ref
Jun 18, 2026
Merged

release: denote AOSP source ref in release title + notes#2
Jawnnypoo merged 1 commit into
mainfrom
release-notes-source-ref

Conversation

@Jawnnypoo

Copy link
Copy Markdown
Member

Follow-up to #1. The published platform-tools-37.0.0 release said "Built from upstream AOSP tag platform-tools-37.0.0" — but that's the release/build-tools name, not the source. It was actually built from android-17.0.0_r1.

This fixes the release job so the notes + title reflect the real AOSP source ref (needs.detect.outputs.source_ref):

  • Notes: "Built from upstream AOSP source tag android-17.0.0_r1."
  • Title: appends the source ref when it diverges from the release name, e.g. platform-tools-37.0.0 (linux-arm64) · android-17.0.0_r1. Legacy releases where the source ref equals the tag (e.g. platform-tools-35.0.2) are unchanged — no redundant suffix.

Affects future releases only; I've separately edited the live platform-tools-37.0.0 release to match.

🤖 Generated with Claude Code

The release name is the build-tools version (platform-tools-X.Y.Z), but
since AOSP's android-NN.0.0_rN scheme the source actually built from
diverges from it — platform-tools-37.0.0 is built from android-17.0.0_r1.
The notes hardcoded "Built from upstream AOSP tag $TAG", which printed
the release name rather than the source. Use the detect job's source_ref
instead, and append it to the title when the two differ (legacy releases
where source_ref == tag are unchanged).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Jawnnypoo Jawnnypoo merged commit 29db41f into main Jun 18, 2026
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.

1 participant