Skip to content

Conversation

itingliu
Copy link
Contributor

@itingliu itingliu commented Sep 5, 2025

With @abi we can make an ABI compatible change so existing clients can continue to work on user's 6.2 devices even after they adopt the correct name on 6.2.1 and above.

But only use @abi for FOUNDATION_FRAMEWORK since ABI compatibility isn't a concern in other scenarios.

@itingliu
Copy link
Contributor Author

itingliu commented Sep 5, 2025

@swift-ci please test

With @abi we can make an ABI compatible change so existing clients can continue to work on user's 6.2 devices even after they adopt the correct name on 6.2.1 and above.

But only use @abi for FOUNDATION_FRAMEWORK since ABI compatibility isn't a concern in other scenarios.
@itingliu itingliu force-pushed the locale-region-rename branch from c988603 to ea56ad4 Compare September 5, 2025 18:09
@itingliu
Copy link
Contributor Author

itingliu commented Sep 5, 2025

@swift-ci please test

@itingliu itingliu merged commit c6793ef into swiftlang:release/6.2.1 Sep 6, 2025
19 checks passed
@itingliu itingliu deleted the locale-region-rename branch September 6, 2025 00:03
itingliu added a commit that referenced this pull request Sep 8, 2025
* Update 6.2.1 package dependency branches (#1496)

* Locale.Region subregion API is misspelled (#1495)

With @abi we can make an ABI compatible change so existing clients can continue to work on user's 6.2 devices even after they adopt the correct name on 6.2.1 and above.

But only use @abi for FOUNDATION_FRAMEWORK since ABI compatibility isn't a concern in other scenarios.

---------

Co-authored-by: Jeremy Schonfeld <[email protected]>
itingliu added a commit that referenced this pull request Sep 9, 2025
* Update 6.2.1 package dependency branches (#1496)

* Locale.Region subregion API is misspelled (#1495)

With @abi we can make an ABI compatible change so existing clients can continue to work on user's 6.2 devices even after they adopt the correct name on 6.2.1 and above.

But only use @abi for FOUNDATION_FRAMEWORK since ABI compatibility isn't a concern in other scenarios.

---------

Co-authored-by: Tina L <[email protected]>
Co-authored-by: Jeremy Schonfeld <[email protected]>
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