fix: bump python core to 3.13.0 #143
Merged
Conversation
This file contains hidden or 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
Codecov Report
@@ Coverage Diff @@
## main #143 +/- ##
=======================================
Coverage 92.84% 92.84%
=======================================
Files 24 24
Lines 21649 21649
=======================================
Hits 20099 20099
Misses 1550 1550 Continue to review full report at Codecov.
|
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Nov 11, 2021
## [0.22.3](v0.22.2...v0.22.3) (2021-11-11) ### Bug Fixes * bump python core to 3.13.0 ([#143](#143)) ([3a2ce15](3a2ce15))
|
🎉 This PR is included in version 0.22.3 🎉 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
This PR bumps up our python core dependency to 3.13.0
PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Does this PR introduce a breaking change?
Other information