PDNS: Added renamed-sdk and deprecation notice #28
Conversation
This file contains 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
csulrong
approved these changes
Oct 29, 2020
|
You can pull the latest changes and it should work |
KumarGanesanIBM
force-pushed
the
dns-prefix
branch
4 times, most recently
from
4f91c3c to
e6c2204
Compare
KumarGanesanIBM
force-pushed
the
dns-prefix
branch
from
e6c2204 to
80df621
Compare
ajay-malhotra1
pushed a commit
that referenced
this pull request
Oct 31, 2020
## [0.11.2](v0.11.1...v0.11.2) (2020-10-31) ### Bug Fixes * PDNS - Added renamed-sdk and deprecation notice ([#28](#28)) ([a3a5aaf](a3a5aaf))
|
🎉 This PR is included in version 0.11.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
PR summary
Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:
PR Type
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?
Other information