fix: updating semver verion to the latest #84
Merged
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
dependency: none Signed-off-by: Joseph Kalandarishvili <[email protected]>
jkalandaibm
force-pushed
the
new-semver-version
branch
from
761ea72 to
22f5e88
Compare
kennburger
approved these changes
Jun 30, 2023
MalarvizhiK
pushed a commit
that referenced
this pull request
Jun 30, 2023
## [0.23.1](v0.23.0...v0.23.1) (2023-06-30) ### Bug Fixes * updating semver version to the latest ([#84](#84)) ([e9b141e](e9b141e))
|
🎉 This PR is included in version 0.23.1 🎉 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.
dependency: none
PR summary
Fixes:
source: https://github.com/IBM/networking-python-sdk/security/dependabot/15
PR Checklist
Please make sure that your PR fulfills the following requirements:
PR Type
What is the current behavior?
one package needed to be updated to the latest.
What is the new behavior?
updated semver package version
Does this PR introduce a breaking change?
Other information