Skip to content

OSOE-1208: Use our own .NET SDKs#101

Open
sarahelsaig wants to merge 11 commits intoissue/OSOE-925from
issue/OSOE-1208
Open

OSOE-1208: Use our own .NET SDKs#101
sarahelsaig wants to merge 11 commits intoissue/OSOE-925from
issue/OSOE-1208

Conversation

@sarahelsaig
Copy link
Copy Markdown
Member

@sarahelsaig sarahelsaig commented Mar 27, 2026

@github-actions
Copy link
Copy Markdown

This pull request appears to contain breaking changes.

  • If you can do this without breaking changes, then please do that, it'd be better.
  • If breaking changes are inevitable, then add an explanation of these and a migration guide for users to the description of the pull request (during the next release, these will be added to the release notes). A CompatibilitySuppressions.xml file was generated for each project with breaking changes that you can download from the artifacts and use to suppress further such warnings.
  • If the changes are technically breaking but not something that would actually be breaking for consuming projects (like the signature of a constructor changing due to new injected dependencies) then also take the generated CompatibilitySuppressions.xml file and add the ignore-breaking-changes label too, the push another commit. Furthermore, consider how in the future this can be avoided: Can perhaps the class be made internal (what's usually better for implementations of interfaces for injected dependencies)?

@github-actions github-actions bot changed the title OSOE-1208: Use our own .NET SDKs OSOE-1208: Use our own .NET SDKs (⚠️ breaking changes) Mar 28, 2026
@sarahelsaig sarahelsaig changed the base branch from dev to issue/OSOE-925 March 28, 2026 20:42
@github-actions github-actions bot changed the title OSOE-1208: Use our own .NET SDKs (⚠️ breaking changes) OSOE-1208: Use our own .NET SDKs Mar 29, 2026
…e text into built-in DescriptionBody suffix.
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