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

Expose optional linter module version info #174

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

atc0005
Copy link
Owner

@atc0005 atc0005 commented Feb 5, 2024

Instead of emitting only the specific release/tag version info, emit the full module version details provided by running "go version -m BINARY".

This is intended to compliment temporary changes to build and package forked copies of the linters provided by the orijtech GitHub Org. The goal is to emit detailed version info until PRs are accepted into the applicable upstream repos to update required dependencies to allow those linters to run using newer Go versions.

At that point the plan is to switch back to emitting only basic module version info since we would be one again using the latest upstream version of the linters.

Instead of emitting only the specific release/tag version
info, emit the full module version details provided by
running "go version -m BINARY".

This is intended to compliment temporary changes to build and
package forked copies of the linters provided by the orijtech
GitHub Org. The goal is to emit detailed version info until PRs
are accepted into the applicable upstream repos to update
required dependencies to allow those linters to run using newer
Go versions.

At that point the plan is to switch back to emitting only basic
module version info since we would be one again using the
latest upstream version of the linters.
@atc0005 atc0005 added the CI label Feb 5, 2024
@atc0005 atc0005 self-assigned this Feb 5, 2024
@atc0005 atc0005 merged commit 21282d2 into master Feb 5, 2024
3 checks passed
@atc0005 atc0005 deleted the expose-optional-linter-module-version-info branch February 5, 2024 13:30
atc0005 added a commit that referenced this pull request Feb 6, 2024
Instead of emitting only the specific release/tag version
info, emit the full module version details provided by
running "go version -m BINARY".

This is intended to compliment temporary changes to build and
package forked copies of the linters called by this workflow.

The goal is to emit detailed version info until PRs
are accepted into the applicable upstream repos to update
required dependencies to allow those linters to run using newer
Go versions.

At that point the plan is to switch back to emitting only basic
module version info since we would be one again using the
latest upstream version of the linters.

refs #174
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant