ci: Version bump workflows

[polarathene]

Related Issues

N/A

Description

Overall, version bumps from most releases in March 2022 to those available in August 2023. Does not appear to introduce any breaking changes that would affect the workflows.

• goreleaser/goreleaser-action is at v4 (the last v2 release was March 2022). Likewise the gorelease version has been bumped from 1.7 (March 2022) to 1.20 (August 2023).
• golangci/golangci-lint-action is at 3.7, but golangci-lint version is presently 1.54. The current 1.45 release is from March 2022.
• spectralops/spectral-github-action v1 was Jan 2022, while Jun 2023 released v4.
• actions/setup-go bumped to v4). Go updated to 1.21 (Aug 2023) from 1.18 (Mar 2022).
• actions/checkout to v4 (Sep 2023).

Motivation and Context

There was a minor update in April 2023 to a workflow, but I felt that the project would benefit from not letting the workflows become stale. At a glance, it doesn't look like there is any breaking changes introduced by any of the dependencies receiving a version bump.

As releases will be built via these workflows, it'd be nice to have them built with a more recent or latest version of Go.

How Has This Been Tested?

I've not tried running these updated workflows via a fork, but the change should be fairly straight-forward / harmless?

[kaplanelad]

Hi @polarathene ,

Thank you for your pull request! Your contribution is much appreciated. 😄

I noticed that the CI tests have failed for this pull request due of linting upgrade. can you please take a look?

[polarathene]

can you please take a look?

Ready for you to run the CI again 👍

[kaplanelad]

I noticed that you made modifications to the files within the vendor/* directory. Regrettably, we cannot accept any additions or alterations in this folder due to security concerns. Our objective is to maintain the integrity of the libraries contained therein, as these libraries are sourced from third-party vendors and should not be subject to any changes.

[polarathene]

Regrettably, we cannot accept any additions or alterations in this folder due to security concerns.

I am not a Go dev, you're asking me to make changes beyond the Github Actions workflow files 🤷‍♂️

• I've reverted the modification to vendor/. I don't know your merge policy, so if you need that squashed I can accommodate.
• Workflow should be fine to run for now to verify everything else is fine?

EDIT: Nevermind, lazy attempt to revert vendor by me. I'll resolve that.

[kaplanelad]

I'm still seeing changes in vendor folder

[polarathene]

I'm still seeing changes in vendor folder

Yeah, sorry about that. Some already had //nolint. Resolved properly.

[polarathene]

goreleaser/goreleaser-action has a v5 release now (nothing too important there, mostly a bump in NodeJS to v20 like many other actions are doing recently), and within a couple days it looks like goreleaser will also have a 1.21 release out.

If the workflows pass and everything looks good, you may want to wait just a little longer to cover that as well?

[kaplanelad]

@polarathene yes it will be great to fix the linting step

[polarathene]

@polarathene yes it will be great to fix the linting step

You do it.

Sorry, but I contributed the PR with no response for 3 weeks, then addressed the review feedback. Tests passed at the time. It's been over 4 months since then, I am not responsible for that drift.

Versions that are bumped in this PR have likely changed since and should be bumped appropriately. I don't use this project, so feel free to update the PR or close it 🤷‍♂️