Skip to content

[deliver] improve documentation & clarify on territory_ids behavior for upload_price_tier#30019

Merged
iBotPeaches merged 1 commit into
fastlane:masterfrom
orbisai0security:fix-v-004-upload-price-tier-empty-territory-ids
May 9, 2026
Merged

[deliver] improve documentation & clarify on territory_ids behavior for upload_price_tier#30019
iBotPeaches merged 1 commit into
fastlane:masterfrom
orbisai0security:fix-v-004-upload-price-tier-empty-territory-ids

Conversation

@orbisai0security

@orbisai0security orbisai0security commented May 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Clarifies the documented behavior of territory_ids when updating app pricing.
The existing behavior intentionally distinguishes between:

  • nil: leave existing territory availability unchanged
  • []: remove the app from sale in all territories
  • non-empty array: update availability to the provided territories

This PR does not change runtime behavior. It only improves documentation/comments so users understand the effect of passing an empty array.

Verification

  • Documentation/comment-only change
  • No runtime behavior changed

🤖 Generated with Claude Code

@iBotPeaches iBotPeaches left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There is a comment in docs that explains this is intentional.

territory_ids = nil # nil won't update app's territory_ids, empty array would remove app from sale.

So this would break that.

@orbisai0security

Copy link
Copy Markdown
Contributor Author

Thanks for the review, that makes sense. I missed that the nil vs empty array behaviour is documented and intentional here.

I agree this PR is too strong because it blocks a valid use case: intentionally passing an empty territory_ids array to remove the app from sale in all territories.

I can close/rework this as a non-security UX/documentation improvement instead, e.g. making the success message more explicit when territory_ids is provided, without changing the documented behaviour.

What would you prefer?

@iBotPeaches

Copy link
Copy Markdown
Member

Yeah I think peeking documentation and ensuring this is documented well could be all we need.

@orbisai0security orbisai0security changed the title fix: the upload_price_tier in upload_price_tier.rb fix: Clarify pricing update message when territory_ids are provided May 8, 2026
@orbisai0security orbisai0security force-pushed the fix-v-004-upload-price-tier-empty-territory-ids branch from 7975fc0 to 2569c05 Compare May 8, 2026 01:59
@orbisai0security orbisai0security changed the title fix: Clarify pricing update message when territory_ids are provided docs: clarify territory_ids behavior for upload_price_tier May 8, 2026
@iBotPeaches iBotPeaches changed the title docs: clarify territory_ids behavior for upload_price_tier [deliver] improve documentation & clarify on territory_ids behavior for upload_price_tier May 9, 2026

@iBotPeaches iBotPeaches left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks. All in all I don't think this is truly needed as it amounted to just rewording a sentence, but since the comment on same line of variable is easier to miss. Going forward.

@iBotPeaches iBotPeaches merged commit 31e3294 into fastlane:master May 9, 2026
9 checks passed

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey @orbisai0security 👋

Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉
The code change now lives in the master branch, however it wasn't released to RubyGems yet.
We usually ship about once a month, and your PR will be included in the next one.

Please let us know if this change requires an immediate release by adding a comment here 👍
We'll notify you once we shipped a new release with your changes 🚀"

PratikPatil131 pushed a commit to PratikPatil131/fastlane that referenced this pull request May 9, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Congratulations! 🎉 This was released as part of fastlane 2.234.0 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants