Skip to content

Allow both platform option in release workflows#385

Merged
ignaciosantise merged 2 commits intomainfrom
feat/release-both-platforms
Feb 13, 2026
Merged

Allow both platform option in release workflows#385
ignaciosantise merged 2 commits intomainfrom
feat/release-both-platforms

Conversation

@ignaciosantise
Copy link
Collaborator

Summary

Add a both platform option to release workflows for AppKit, WalletKit, and Mobile POS (both variants). This allows releasing on both Android and iOS simultaneously with a single workflow trigger.

The both option is now the default selection for improved user experience.

Changes

  • Added both to platform choices in 4 workflow files (listed first as default)
  • Updated run-name to display "🍎 iOS & 🤖 Android" when both is selected
  • Updated job conditions to trigger both Android and iOS builds when both is selected
  • For POS workflows, preserved the existing tag-push behavior for automatic Android builds

🤖 Generated with Claude Code

Allow releasing AppKit, WalletKit, and POS on both Android and iOS simultaneously with a single workflow trigger. The 'both' option is now the default selection.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings February 13, 2026 17:27
@vercel
Copy link

vercel bot commented Feb 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
react-native-examples Ready Ready Preview, Comment Feb 13, 2026 6:16pm

Request Review

@claude
Copy link

claude bot commented Feb 13, 2026

Claude finished @ignaciosantise's task in 41s —— View job


Review Complete

  • Read modified workflow files
  • Check for security issues and best practices
  • Verify consistency across workflows
  • Provide review feedback

✅ No issues found

Changes are consistent across all 4 workflows:

  • both option correctly added as first choice (default)
  • run-name properly handles all 3 platform cases
  • Job conditions correctly trigger for android, ios, or both
  • POS workflow preserves tag-push behavior for automatic Android builds (line 25)

Logic verified:

  • AppKit/WalletKit: Simple OR logic for both jobs
  • POS: Android includes push event OR platform selection
  • POS: iOS excludes push events AND checks platform selection
  • POS PoC: Matches POS logic without push trigger

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds a both platform option to release workflows for AppKit, WalletKit, and Mobile POS (including the PoC variant), allowing simultaneous releases on both Android and iOS platforms. The both option is positioned as the first (default) choice in the dropdown menu for improved user experience.

Changes:

  • Added both as the first platform option in workflow input choices
  • Updated run-name expressions to display "🍎 iOS & 🤖 Android" when both is selected
  • Modified job conditionals to trigger both Android and iOS builds when both is selected

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File Description
.github/workflows/release-walletkit.yaml Added both platform option with updated run-name and job conditions
.github/workflows/release-appkit.yaml Added both platform option with updated run-name and job conditions
.github/workflows/release-pos.yaml Added both platform option with updated run-name and job conditions, preserving tag-push behavior
.github/workflows/release-pos-poc.yaml Added both platform option with updated run-name and job conditions

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ignaciosantise ignaciosantise merged commit 29a464c into main Feb 13, 2026
6 checks passed
@ignaciosantise ignaciosantise deleted the feat/release-both-platforms branch February 13, 2026 18:25
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