Skip to content

feat(2023-02-14): Update SDK to use API generated on 2023-02-14 and semantic release fix #51

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 1 commit into from
Feb 20, 2023

Conversation

deepaksibm
Copy link
Member

semantic release fix
As per https://github.com/semantic-release/semantic-release/releases/tag/v20.0.0
and semantic-release/semantic-release@c7b8e10

semantic-release now needs node v18 as the minimum required version.

updating the nvm command to nvm install --lts to always install the latest time term support version

distro upgraded from xeniel to focus to support node 18

@deepaksibm deepaksibm merged commit dc7aba0 into master Feb 20, 2023
@deepaksibm deepaksibm deleted the semantic-release-fix branch February 20, 2023 05:40
ibm-vpc pushed a commit that referenced this pull request Feb 20, 2023
# [0.15.0](v0.14.0...v0.15.0) (2023-02-20)

### Features

* **2023-02-14:** Update SDK to use API generated on 2023-02-14 ([#49](#49)) ([ea5dc20](ea5dc20))
* **2023-02-14:** Update SDK to use API generated on 2023-02-14 and semantic release fix ([#50](#50)) ([1fe4314](1fe4314))
* **2023-02-14:** Update SDK to use API generated on 2023-02-14 and semantic release fix ([#51](#51)) ([dc7aba0](dc7aba0))
@ibm-vpc
Copy link
Collaborator

ibm-vpc commented Feb 20, 2023

🎉 This PR is included in version 0.15.0 🎉

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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants