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

update to latest go version #2

Merged
merged 2 commits into from
Jun 26, 2024
Merged

update to latest go version #2

merged 2 commits into from
Jun 26, 2024

Conversation

dandersonsw
Copy link

@dandersonsw dandersonsw commented Jun 26, 2024

Changes proposed in this pull request:

  • Update to use latest go version and modules
  • Add security considerations file

Things to check

  • For any logging statements, is there any chance that they could be logging sensitive data?
  • Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

Security considerations

Update go version and modules. Adds security considerations file.

@dandersonsw dandersonsw requested a review from a team June 26, 2024 18:20
@dandersonsw dandersonsw merged commit 529c2a0 into main Jun 26, 2024
2 checks passed
@dandersonsw dandersonsw deleted the update-go branch June 26, 2024 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants