Skip to content

internal/go/cache: update ProgRequest #5575

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

Closed
5 of 7 tasks
pierrre opened this issue Mar 18, 2025 · 1 comment · Fixed by #5576
Closed
5 of 7 tasks

internal/go/cache: update ProgRequest #5575

pierrre opened this issue Mar 18, 2025 · 1 comment · Fixed by #5576
Assignees

Comments

@pierrre
Copy link
Contributor

pierrre commented Mar 18, 2025

Welcome

  • Yes, I'm using a binary release within 2 latest releases. Only such installations are supported.
  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've read the typecheck section of the FAQ.
  • Yes, I've tried with the standalone linter if available (e.g., gocritic, go vet, etc.).
  • I agree to follow this project's Code of Conduct

How did you install golangci-lint?

Official binary

Description of the problem

See https://pkg.go.dev/cmd/go/internal/cacheprog

The ObjectID field is deprecated and there is now OutputID.

Version of golangci-lint

$ golangci-lint --version
# Paste output here

Configuration

# paste configuration file or CLI flags here

Go environment

$ go version && go env
# paste output here

Verbose output of running

$ golangci-lint cache clean
$ golangci-lint run -v
# paste output here

A minimal reproducible example or link to a public repository

// add your code here

Validation

  • Yes, I've included all information above (version, config, etc.).

Supporter

@pierrre pierrre added the bug Something isn't working label Mar 18, 2025
@ldez ldez removed the bug Something isn't working label Mar 18, 2025
@ldez ldez self-assigned this Mar 18, 2025
@pierrre
Copy link
Contributor Author

pierrre commented Mar 18, 2025

Thank you !

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

Successfully merging a pull request may close this issue.

2 participants