-
Notifications
You must be signed in to change notification settings - Fork 7
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
Build multiple go versions #3
Conversation
255d1d5
to
2755b8c
Compare
Signed-off-by: Carlos Eduardo Arango Gutierrez <[email protected]>
2755b8c
to
d285dd7
Compare
@@ -12,7 +12,7 @@ | |||
# See the License for the specific language governing permissions and | |||
# limitations under the License. | |||
|
|||
ARG GOLANG_VERSION=x.x.x | |||
ARG GOLANG_VERSION=x.x |
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.
Nit: Why the change?
@@ -31,9 +31,11 @@ on: | |||
jobs: | |||
build: | |||
runs-on: ubuntu-latest | |||
strategy: | |||
matrix: | |||
go-version: ["1.21","1.20","1.19"] |
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 don't quite agree with this. For "reasons" we're still on 1.20.4
on some projects, so we may want to pin particular minor versions. We also refer to the full version in all consumers.
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.
this is an image for running CI tools, I don't see the advantage of a point release here.
I agree production images for a specific component could be tied to a specific version, but for CI steps, the generic 1.x.latest should be ok
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.
Let us make this change at a later stage if required. For now, let's match what we currently do -- which is to use a point release.
No description provided.