Skip to content

fix: Fix travis failure #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Dec 12, 2024
Merged

fix: Fix travis failure #124

merged 5 commits into from
Dec 12, 2024

Conversation

jkalandaibm
Copy link
Collaborator

@jkalandaibm jkalandaibm commented Dec 11, 2024

PR summary

Fixes:
image

source: https://app.travis-ci.com/github/IBM/networking-python-sdk/jobs/628905973

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

jkalandaibm and others added 4 commits December 11, 2024 17:17
dependency: none
Signed-off-by: jkalanda <[email protected]>
dependency: none
Signed-off-by: jkalanda <[email protected]>
## [0.27.2](v0.27.1...v0.27.2) (2024-12-10)

### Bug Fixes

* fixing travis failure ([#123](#123)) ([2db019e](2db019e))

Signed-off-by: jkalanda <[email protected]>
@jkalandaibm jkalandaibm merged commit 11fc2af into master Dec 12, 2024
3 checks passed
@kennburger kennburger deleted the fix-travis branch December 12, 2024 17:57
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