Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge v.next into main for 200.3 #532

Merged
merged 508 commits into from
Dec 6, 2023
Merged

Merge v.next into main for 200.3 #532

merged 508 commits into from
Dec 6, 2023

Conversation

des12437
Copy link
Contributor

@des12437 des12437 commented Dec 4, 2023

All issues found during testing and certification have been resolved or triaged for next release. Please test with SPM.

@des12437 des12437 self-assigned this Dec 4, 2023
@des12437 des12437 marked this pull request as ready for review December 4, 2023 23:53
@mhdostal
Copy link
Member

mhdostal commented Dec 5, 2023

@des12437 One other thing to do once the SDK and Developer Doc is released is to make sure the links to the doc all work correctly, both in the 200.3 Release notes and the Toolkit repo's README.md

Copy link
Collaborator

@dfeinzimer dfeinzimer left a comment

Choose a reason for hiding this comment

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

200.3 builds okay with SPM

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.

10 participants