Skip to content

ci: trigger maven release for new tags #337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joe-p wants to merge 5 commits into
base: main
Choose a base branch
from
Open

ci: trigger maven release for new tags #337

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
1291d6f
chore: format
joe-p Mar 18, 2026
fcf516d
chore: update gradle namespaces
joe-p Mar 18, 2026
fa0f08b
ci: maven release on tag
joe-p Mar 22, 2026
b164b31
chore: rm algo25 packages
joe-p Mar 22, 2026
82876d3
ci: mavenPublishing
joe-p Mar 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/workflows/android_ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ on:
description: "Crate name to build Android package from"
required: true
type: string
release:
description: "Whether to build a release version"
required: true
type: boolean
Comment on lines +10 to +13
Copy link

Copilot AI Mar 22, 2026

Choose a reason for hiding this comment

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

release is a required input but is not used anywhere in the job (the build, artifact path, and publish behavior are currently identical regardless of its value). Either make it optional with a default (e.g., false) and use it to control release-only steps, or remove the input to avoid misleading callers.

Copilot uses AI. Check for mistakes.

env:
CRATE: ${{ inputs.crate }}
Expand Down Expand Up @@ -76,3 +80,17 @@ jobs:
with:
name: ${{ env.CRATE }}.aar
path: ${{ env.ANDROID_PACKAGE_DIR }}/build/outputs/aar/${{ env.CRATE }}-release.aar

- name: Build and Publish to Maven Central
working-directory: ${{ env.ANDROID_PACKAGE_DIR }}
env:
GITHUB_TAG: ${{ github.ref_name }}
ORG_GRADLE_PROJECT_signingInMemoryKey: ${{ secrets.RSA_GPG_PRIVATE_KEY }}
ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.RSA_GPG_PASSPHRASE }}
ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.CENTRAL_USERNAME }}
ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.CENTRAL_PASSWORD }}
run: |
export VERSION_TAG=${GITHUB_TAG#v} # Remove the leading 'v'
echo "Publishing version: $VERSION_TAG"
echo "Publishing to Maven Central (USER_MANAGED - requires manual release)..."
./gradlew publishToMavenCentral
Comment on lines +84 to +96
Copy link

Copilot AI Mar 22, 2026

Choose a reason for hiding this comment

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

The Maven publish step runs unconditionally, so it will execute on pull_request and on normal pushes to main as well (where github.ref_name is main). That will both fail due to missing secrets on PRs and attempt to publish an invalid version derived from a non-tag ref. Gate this step with if: inputs.release (and ideally also github.ref_type == 'tag') and only derive the version from the tag when publishing.

Copilot uses AI. Check for mistakes.
3 changes: 3 additions & 0 deletions .github/workflows/ci_cd.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ on:
push: # A push indicates that a PR is merged and CD should be triggered
branches:
- main
tags:
- 'v*'
Comment on lines 4 to +8
Copy link

Copilot AI Mar 22, 2026

Choose a reason for hiding this comment

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

Adding a push.tags trigger means this workflow now runs on tag pushes as well as branch pushes. Because other jobs in this workflow treat any push as a release signal (e.g., swift_ci uses release: ${{ github.event_name == 'push' }}), tagging will unintentionally enable those release behaviors too. If the intent is to release only Android on tag pushes, tighten those release: conditions to exclude tags (or split tag-triggered release into a separate workflow).

Copilot uses AI. Check for mistakes.
pull_request: # For PRs, we run CI, which is the same as CD without the release step(s)
branches:
- main
Expand Down Expand Up @@ -96,3 +98,4 @@ jobs:
include: ${{ fromJSON(needs.setup.outputs.ffi_packages) }}
with:
crate: ${{ matrix.crate_name }}
release: ${{ github.event_name == 'push' && github.ref_type == 'tag' }}
43 changes: 0 additions & 43 deletions packages/android/algokit_algo25/README.md
View file
Open in desktop

This file was deleted.

53 changes: 0 additions & 53 deletions packages/android/algokit_algo25/build.gradle.kts
View file
Open in desktop

This file was deleted.

7 changes: 0 additions & 7 deletions packages/android/algokit_algo25/gradle.properties
View file
Open in desktop

This file was deleted.

24 changes: 0 additions & 24 deletions packages/android/algokit_algo25/gradle/libs.versions.toml
View file
Open in desktop

This file was deleted.

Binary file removed packages/android/algokit_algo25/gradle/wrapper/gradle-wrapper.jar
View file
Open in desktop
Binary file not shown.
7 changes: 0 additions & 7 deletions packages/android/algokit_algo25/gradle/wrapper/gradle-wrapper.properties
View file
Open in desktop

This file was deleted.

Loading
Loading