Skip to content

Conversation

d-ronnqvist
Copy link
Contributor

Bug/issue #, if applicable:

Summary

Now that version 5.10 is released, API that's been deprecated during the 5.9 release can be removed according to the process described in the "Introducing source breaking changes" section of CONTRIBUTING.md.

The plan is to not cherry-pick this into the 6.0 release branch, so in practice we kept this API around for longer than what the deprecation message communicated.

This also updates the deprecation message for API that said that it would be removed after "5.11" is release to instead say that it will be removed after "6.0" is released now that we know that there is no 5.11 version (6.0 is the version after 5.10).

Some API was incorrectly annotated to say that it will be removed after 5.12 is released. This API was deprecated during the 5.10 release, meaning that our guideline would be to remove it after 6.0 (what was known as 5.11) is released. These have also been updated to "6.0".

Dependencies

None.

Testing

Nothing in particular. DocC itself wasn't using this API anymore.

Checklist

Make sure you check off the following items. If they cannot be completed, provide a reason.

  • [ ] Added tests
  • Ran the ./bin/test script and it succeeded
  • [ ] Updated documentation if necessary

The release after 5.10 is not 5.11 but 6.0.
The API said 5.12 in their deprecation message was really deprecated during the 5.10 release and should have said 5.11 as the version the API will be removed.
@d-ronnqvist d-ronnqvist added the code cleanup Code cleanup *without* user facing changes label Mar 18, 2024
@d-ronnqvist
Copy link
Contributor Author

@swift-ci please test

@d-ronnqvist d-ronnqvist merged commit 3e0c8e2 into swiftlang:main Mar 19, 2024
@d-ronnqvist d-ronnqvist deleted the remove-api-deprecated-before-5.10 branch March 19, 2024 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

code cleanup Code cleanup *without* user facing changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants