Skip to content

Add build/version number overrides to iOS actions#80

Merged
ssestak merged 4 commits intomainfrom
feature/custom-build-version-overrides
Feb 23, 2026
Merged

Add build/version number overrides to iOS actions#80
ssestak merged 4 commits intomainfrom
feature/custom-build-version-overrides

Conversation

@ssestak
Copy link
Contributor

@ssestak ssestak commented Feb 17, 2026

Summary

Add optional build_number and version_number inputs to iOS Fastlane beta and release actions, and wire them through the on-demand build workflow. This lets consumers override auto-incremented build numbers and default versions without modifying Fastlane configuration.

Changes

  • Release action now parses version tags via parse-version-tag.sh — strips suffixes (1.2.3-beta.11.2.3)
  • Both beta and release scripts conditionally build FASTLANE_ARGS from the new inputs
  • BATS tests cover version tag parsing, beta, and release argument forwarding

Notes

Do not merge until pull request in the Futured fastlane repository is merged, since the fastlane API will not be ready.

Diagram

View diagram
flowchart TD
    A["Workflow Inputs<br/>build_number, version_number"] --> B{"Action type"}
    B -->|Beta| C["ios-fastlane-beta"]
    B -->|Release| D["ios-fastlane-release"]
    D --> E["parse-version-tag.sh<br/>x.y.z-* → x.y.z"]
    E --> F["release.sh"]
    C --> G["beta.sh"]
    G --> H["Build FASTLANE_ARGS<br/>conditionally from inputs"]
    F --> H
    H --> I["fastlane beta/release<br/>build_number:X version_number:Y"]
Loading

🤖 Generated with Claude Code

Šimon Šesták and others added 3 commits February 17, 2026 11:33
Add optional build_number and version_number inputs to ios-fastlane-beta
and ios-fastlane-release actions, and to the on-demand build workflow.

The release action now parses version tags in x.y.z-k format to
automatically extract build numbers from tags, while explicit
build_number input takes precedence.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Stop extracting build_number from version tags — it now only comes from
the explicit build_number input. The tag regex accepts any suffix after
the first dash (e.g. 1.2.3-beta, 1.2.3-rc1) and extracts only the
x.y.z portion as version_number.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Document the relaxed version tag format (x.y.z-* suffix ignored) and
that build_number is never derived from tags. Add release action BATS
test commands to the testing section.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ssestak ssestak changed the title Custom build version overrides Add build/version number overrides to iOS actions Feb 19, 2026
@ssestak ssestak requested a review from jmarek41 February 19, 2026 14:29
Copy link
Member

@jmarek41 jmarek41 left a comment

Choose a reason for hiding this comment

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

👏

Replace verbose string concatenation with array-based arg building,
removing the shellcheck disable directive. Addresses PR #80 readability feedback.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ssestak ssestak merged commit fa7712b into main Feb 23, 2026
2 checks passed
@ssestak ssestak deleted the feature/custom-build-version-overrides branch February 23, 2026 14:57
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.

2 participants