-
Notifications
You must be signed in to change notification settings - Fork 61
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
fix: enable builds on windows #273
Conversation
563a6a7
to
960b63d
Compare
@michaelbeck Hi Michael, this is the PR for the Go SDK to provide a little more detail for Windows users. I don't think there was really all that much to change, other than including details of the prereqs (note that I am performing these steps in a powershell window within my Windows 11 VM to keep me honest 😂 ). Let me know if you think more details are needed. Thanks! |
This commit updates the project to enable builds to be performed on Windows. I also bumped the go core version to the current latest. Signed-off-by: Phil Adams <phil_adams@us.ibm.com>
960b63d
to
2f84eaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works well here! 👍
## [0.47.1](v0.47.0...v0.47.1) (2023-08-31) ### Bug Fixes * enable builds on windows ([#273](#273)) ([b39d2d5](b39d2d5))
🎉 This PR is included in version 0.47.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This commit updates the project to enable builds to be performed on Windows. I also bumped the go core version to the current latest. Signed-off-by: Phil Adams <phil_adams@us.ibm.com> Signed-off-by: manu.k.m <manu.k.m@ibm.com>
## [0.47.1](IBM/platform-services-go-sdk@v0.47.0...v0.47.1) (2023-08-31) ### Bug Fixes * enable builds on windows ([IBM#273](IBM#273)) ([b39d2d5](IBM@b39d2d5)) Signed-off-by: manu.k.m <manu.k.m@ibm.com>
PR summary
This PR updates the project to allow builds to be done on Windows.
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