[GH-ISSUE #692] feat(metadata): fastlane deliver parity behaviors in asc style #190

Closed
opened 2026-02-26 21:33:57 +03:00 by kerem · 0 comments
Owner

Originally created by @rudrankriyam on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/692

Parent

Summary

Close key fastlane deliver behavior gaps while preserving asc principles (explicit flags, JSON-first, non-interactive).

Parity Goals

Support equivalent workflows for teams currently using fastlane metadata conventions, including edge semantics that affect migration fidelity.

Scope (Parity Behaviors)

  • Default locale semantics (default fallback expansion) with explicit asc controls.
  • Fastlane review-information compatibility:
    • review_information/*.txt ingestion/mapping
    • legacy key aliases where needed
  • Non-localized metadata compatibility where applicable.
  • Deliverfile-aware behavior for migration contexts (metadata_path, skip toggles already partially supported).
  • Clear policy docs for any intentional non-parity behavior.

Detailed Tasks

  • Define parity matrix: fastlane behavior -> asc behavior -> status.
  • Implement configurable default-locale expansion in canonical metadata model.
  • Implement review-information mapping with explicit schemas.
  • Add compatibility handling for legacy/alias field names where required.
  • Document intentional divergences with rationale.

Test Plan (TDD)

  • Cmdtest: default-locale expansion produces expected per-locale effective payloads.
  • Cmdtest: review information files map correctly and deterministically.
  • Unit: legacy alias handling resolves to canonical keys.
  • Unit: parity matrix fixtures validate expected asc behavior for representative fastlane inputs.

Acceptance Criteria

  • High-impact fastlane metadata behaviors are supported or explicitly documented as non-goals.
  • Compatibility behavior is deterministic and tested.
  • Migration users can predict asc behavior from fastlane inputs.

Out of Scope

  • Full fastlane binary/TestFlight lane parity beyond metadata synchronization domain.
Originally created by @rudrankriyam on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/692 ## Parent - #587 - Depends on #687 - Depends on #691 ## Summary Close key fastlane `deliver` behavior gaps while preserving `asc` principles (explicit flags, JSON-first, non-interactive). ## Parity Goals Support equivalent workflows for teams currently using fastlane metadata conventions, including edge semantics that affect migration fidelity. ## Scope (Parity Behaviors) - Default locale semantics (`default` fallback expansion) with explicit `asc` controls. - Fastlane review-information compatibility: - `review_information/*.txt` ingestion/mapping - legacy key aliases where needed - Non-localized metadata compatibility where applicable. - Deliverfile-aware behavior for migration contexts (`metadata_path`, skip toggles already partially supported). - Clear policy docs for any intentional non-parity behavior. ## Detailed Tasks - [ ] Define parity matrix: `fastlane behavior -> asc behavior -> status`. - [ ] Implement configurable default-locale expansion in canonical metadata model. - [ ] Implement review-information mapping with explicit schemas. - [ ] Add compatibility handling for legacy/alias field names where required. - [ ] Document intentional divergences with rationale. ## Test Plan (TDD) - [ ] Cmdtest: default-locale expansion produces expected per-locale effective payloads. - [ ] Cmdtest: review information files map correctly and deterministically. - [ ] Unit: legacy alias handling resolves to canonical keys. - [ ] Unit: parity matrix fixtures validate expected asc behavior for representative fastlane inputs. ## Acceptance Criteria - [ ] High-impact fastlane metadata behaviors are supported or explicitly documented as non-goals. - [ ] Compatibility behavior is deterministic and tested. - [ ] Migration users can predict asc behavior from fastlane inputs. ## Out of Scope - Full fastlane binary/TestFlight lane parity beyond metadata synchronization domain.
kerem 2026-02-26 21:33:57 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/App-Store-Connect-CLI#190
No description provided.