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

updated go version to 1.21 #225

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

Adarsh-jaiss
Copy link
Member

Changes

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 13, 2024
@Adarsh-jaiss
Copy link
Member Author

  • Hey @SaschaSchwarze0 , I Saw this issue need to be fixed for the next milestone, so i fixed it :)
  • Please review it and do let me know if there are other changes to make, also i have fixed it keeping in mind the previous PR :)

@qu1queee qu1queee self-requested a review March 14, 2024 08:19
@@ -43,7 +43,7 @@ jobs:
- name: Run GoReleaser
uses: goreleaser/goreleaser-action@v2
with:
version: v1.18.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

im not too sure about this being ideal, I opened #227 so dependabot can take care of it.

Copy link
Contributor

@HeavyWombat HeavyWombat Mar 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this will not be tackled by the Dependabot automation. I would actually suggest to remove the version here as we don't want to pin the GoReleaser version unless we have a very good reason. Omitting the value means we default to latest anyway.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But good catch that this value is clearly wrong here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But we have a good reason to pin the GoReleaser version: #204. We should have maybe created an issue at that time, though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't aware, or I forgot about it. But I would suggest we just fix the issue: #233 to get out of that pinning.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Adarsh-jaiss Now that we have all understood the implications and with #233 being merged, can you rebase your PR one more time? The change of the version here is no longer needed. Thanks!

@@ -43,7 +43,7 @@ jobs:
- name: Run GoReleaser
uses: goreleaser/goreleaser-action@v2
with:
version: v1.18.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Adarsh-jaiss Now that we have all understood the implications and with #233 being merged, can you rebase your PR one more time? The change of the version here is no longer needed. Thanks!

@Adarsh-jaiss
Copy link
Member Author

Adarsh-jaiss commented Mar 15, 2024

Hey @HeavyWombat , I'm unable to see the previous commits in my local development enviroment, and in order to rebase this, i need to do that, but now i am stuck!
please take a look at this, and please help me out to fix :
image

otherwise, the only soltuion i have now it to make a new fresh PR with clean changes :(

Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look fine. @HeavyWombat if you insist on your commit history requirement, please work with @Adarsh-jaiss.

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2024
Signed-off-by: adarsh-jaiss <[email protected]>
Copy link
Contributor

@HeavyWombat HeavyWombat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2024
Copy link
Contributor

openshift-ci bot commented Mar 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HeavyWombat, SaschaSchwarze0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [HeavyWombat,SaschaSchwarze0]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 81df7a5 into shipwright-io:main Mar 25, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

[FEATURE] Update to Go 1.21
4 participants