Skip to content

Conversation

@jnunn-aws
Copy link
Contributor

Description

This is the first PR for any repo to implement the additional assessment criteria for breaking changes. The team pre-approved the verbiage used here, however, this is a good opportunity to revise it before it is copied to other repos/branches so please take this into consideration before approving.

Motivation and Context

DOTNET-8366

Testing

No testing performed / Documentation only.

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation only

Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed

License

  • I confirm that this pull request can be released under the Apache 2 license

@dscpinheiro dscpinheiro changed the base branch from main to development December 24, 2025 23:41

## Breaking Changes Assessment

1. Identify all breaking changes including the following details:
Copy link
Contributor

Choose a reason for hiding this comment

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

Based on the Sev 2 related to ServiceFullName, I think we should explicitly call out Have you validated version incompatibilities between AWSSDK.Core and service packages? (e.g. new AWSSDK.Core and old service package)

We should also perhaps add link to Wiki section mentioning list of common breaking changes what should NOT be done at any cost.

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