Move changes introduced by #18571 to 2026.1#18804
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR corrects the placement of API deprecation changes from PR #18571 by moving them from the 2025.3 section to the proper 2026.1 section in the changes documentation.
- Moved deprecation notices for hwPortUtils symbols to the correct version section
- Removed duplicate entries from the 2025.3 section
- Ensured proper chronological organization of API changes
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
seanbudd
approved these changes
Aug 25, 2025
5 tasks
SaschaCowley
added a commit
that referenced
this pull request
Aug 25, 2025
### Link to issue number: Follow-up to #18571 Follow-up to #18804 ### Summary of the issue: There were a few errors in the changes introduced by #18571 that weren't caught in #18804. ### Description of user facing changes: None ### Description of developer facing changes: Cosmetic fixes to changes introduced in #18571. ### Description of development approach: Merge 2 change log items, add missing asterisk. ### Testing strategy: None ### Known issues with pull request: None ### Code Review Checklist: - [x] Documentation: - Change log entry - User Documentation - Developer / Technical Documentation - Context sensitive help for GUI changes - [x] Testing: - Unit tests - System (end to end) tests - Manual testing - [x] UX of all users considered: - Speech - Braille - Low Vision - Different web browsers - Localization in other languages / culture than English - [x] API is compatible with existing add-ons. - [x] Security precautions taken.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Follow-up to #18571
Summary of the issue:
#18571 erroneously included its API changes in the 2025.3 section of the changes file.
Description of user facing changes:
None
Description of developer facing changes:
API changes are correctly included in the 2026.1 section of the changes file.
Description of development approach:
Moved lines.
Testing strategy:
None needed.
Known issues with pull request:
None.
Code Review Checklist: