android / android/ndk

[FR] make RC-status of releases a real part of the NDK

Open
#2,126 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
2.3k
Forks
310
PR merge metrics
No merged PRs in 30d

Description

### Description

I need to download the latest one automatically with .

```bash
#!/bin/bash

# Get the latest release tag from the remote repository
latest_tag=$(git ls-remote --tags https://github.com/android/ndk.git | awk -F'/' '{print $NF}' | sort -V | tail -n1)

# Store the tag in the variable
ANDROIDNDKVERSION=$latest_tag

# Print the variable to verify
echo "The latest release tag is: $ANDROIDNDKVERSION"
```

https://github.com/android/ndk/releases/tag/r28-rc2

This correlates to https://dl.google.com/android/repository/android-ndk-r28-beta3-linux.zip not https://dl.google.com/android/repository/android-ndk-r28-rc2-linux.zip

while

https://github.com/android/ndk/releases/tag/r28-beta1
is the name as its download file name.

### I am using a supported NDK

- [x] I have checked and the NDK I'm using is currently supported

### Affected versions

r28

Contributor guide

Open the contributing guide

Research direction

Start by comparing the r28-rc2 and r28-beta1 release tags with their corresponding download URLs, as shown in the issue. Trace the NDK release metadata or publishing entry point responsible for this mapping; done means RC releases resolve to download filenames that include the RC status consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.