Skip to content
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

Merged
merged 1 commit into from
Jan 25, 2024
Merged

Build multiple go versions #3

merged 1 commit into from
Jan 25, 2024

Conversation

ArangoGutierrez
Copy link
Collaborator

No description provided.

Signed-off-by: Carlos Eduardo Arango Gutierrez <[email protected]>
@ArangoGutierrez ArangoGutierrez merged commit 96d8a11 into main Jan 25, 2024
3 checks passed
@ArangoGutierrez ArangoGutierrez deleted the images branch January 25, 2024 16:30
@@ -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
Copy link
Member

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"]
Copy link
Member

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.

Copy link
Collaborator Author

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

Copy link
Member

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.

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