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

chore: Bump golangci-lint to v1.59.1 #42049

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

@tigrato tigrato changed the title chore: chore: Bump golangci-lint to v1.59.0 chore: Bump golangci-lint to v1.59.0 May 27, 2024
@tigrato
Copy link
Contributor Author

tigrato commented May 27, 2024

Blocked by go-simpler/sloglint#45

Copy link
Contributor

@codingllama codingllama left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for doing this.

.golangci.yml Outdated Show resolved Hide resolved
@tigrato tigrato force-pushed the tigrato/chore-upgrade-golangcilint branch from a5c0004 to 993c4c9 Compare June 9, 2024 20:22
@tigrato tigrato force-pushed the tigrato/chore-upgrade-golangcilint branch from 993c4c9 to b27bf08 Compare June 9, 2024 20:23
@tigrato tigrato changed the title chore: Bump golangci-lint to v1.59.0 chore: Bump golangci-lint to v1.59.1 Jun 9, 2024
@tigrato tigrato added the no-changelog Indicates that a PR does not require a changelog entry label Jun 9, 2024
@tigrato tigrato marked this pull request as ready for review June 9, 2024 20:35
@tigrato tigrato added this pull request to the merge queue Jun 10, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jun 10, 2024
@tigrato tigrato added this pull request to the merge queue Jun 10, 2024
Merged via the queue into master with commit bdb5d1a Jun 10, 2024
46 checks passed
@tigrato tigrato deleted the tigrato/chore-upgrade-golangcilint branch June 10, 2024 14:31
@public-teleport-github-review-bot

@tigrato See the table below for backport results.

Branch Result
branch/v13 Failed
branch/v14 Failed
branch/v15 Failed
branch/v16 Create PR

tigrato added a commit that referenced this pull request Jun 22, 2024
The `source` key in slog.Logger is a reserved key and should not be used because it causes a panic.
This commit removes the `source` key from the logger.

Note: We already enforce the forbidden keys as per #42049.
However, our lint jobs currently only run on Ubuntu runners, while the code in question compiles for Darwin targets only.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
github-merge-queue bot pushed a commit that referenced this pull request Jun 22, 2024
The `source` key in slog.Logger is a reserved key and should not be used because it causes a panic.
This commit removes the `source` key from the logger.

Note: We already enforce the forbidden keys as per #42049.
However, our lint jobs currently only run on Ubuntu runners, while the code in question compiles for Darwin targets only.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
github-actions bot pushed a commit that referenced this pull request Jun 22, 2024
The `source` key in slog.Logger is a reserved key and should not be used because it causes a panic.
This commit removes the `source` key from the logger.

Note: We already enforce the forbidden keys as per #42049.
However, our lint jobs currently only run on Ubuntu runners, while the code in question compiles for Darwin targets only.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
github-merge-queue bot pushed a commit that referenced this pull request Jun 22, 2024
The `source` key in slog.Logger is a reserved key and should not be used because it causes a panic.
This commit removes the `source` key from the logger.

Note: We already enforce the forbidden keys as per #42049.
However, our lint jobs currently only run on Ubuntu runners, while the code in question compiles for Darwin targets only.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants