Summary

Adds a new update_app_age_rating action for standalone App Store Connect age rating updates.

This follows the discussion in #30017, where maintainer @iBotPeaches suggested introducing a dedicated action (similar to match_nuke) instead of extending the existing skip_metadata behavior.

Motivation

Age ratings are app-level metadata and can be updated independently from screenshots, descriptions, or binary uploads.

Currently, automating an age rating update through fastlane requires invoking the broader deliver metadata flow, even when only the age rating declaration needs to change.

This action provides a lightweight and explicit workflow for that use case.

Changes

• Added update_app_age_rating action
• Added RSpec coverage for success and failure paths

Implementation Details

The action:

1. Authenticates using either:

   • App Store Connect API key
   • Apple ID session fallback

2. Finds the app via bundle identifier

3. Fetches editable AppInfo

4. Parses the supplied JSON configuration

5. Reuses existing AgeRatingDeclaration mapping helpers already used by deliver

6. Updates the age rating declaration via Spaceship

No new Spaceship API surface was introduced.

Example

update_app_age_rating(
  api_key_path: "fastlane/api_key.json",
  app_identifier: "com.example.app",
  age_rating_config_path: "fastlane/metadata/age_rating.json"
)

Testing

bundle exec rspec fastlane/spec/update_app_age_rating_spec.rb

bundle exec rubocop fastlane/lib/fastlane/actions/update_app_age_rating.rb

bundle exec rubocop fastlane/spec/update_app_age_rating_spec.rb

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a
• I see green ci/circleci builds passing
• I've read the Contribution Guidelines
• I've added/updated relevant unit tests
• I've updated the CHANGELOG