-
Notifications
You must be signed in to change notification settings - Fork 45
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
update go version in SDK and example project #816
update go version in SDK and example project #816
Conversation
No New Or Fixed Issues Found |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #816 +/- ##
=======================================
Coverage 58.55% 58.55%
=======================================
Files 178 178
Lines 11405 11405
=======================================
Hits 6678 6678
Misses 4727 4727 ☔ View full report in Codecov by Sentry. |
@@ -11,7 +11,7 @@ on: | |||
|
|||
env: | |||
GO111MODULE: on | |||
GO_VERSION: "^1.18" | |||
GO_VERSION: "^1.21" |
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.
The build and release workflows were already building with Go 1.22.3
prior to this change. This is merely updating the workflows to match the minimum Go versions supported in our module.
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.
I have little impact on this review, but do like to see that we've aligned on versions and can maintain the dependencies accurately!
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.
Nice, LGTM!
🎟️ Tracking
https://bitwarden.atlassian.net/browse/SM-1288
📔 Objective
Follow-up of SM-1288 to update the Go version requirements in our wrapper and example project.
⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes