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.

Sign up for GitHub

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

Jump to bottom

Bump gopkg.in/yaml.v3 #245

Merged
merged 1 commit into from
May 31, 2022
Merged

Bump gopkg.in/yaml.v3 #245

merged 1 commit into from
May 31, 2022

Conversation

thomaspoignant
Copy link
Owner

Description

Security issue with gopkg.in/yaml.v3, bumping to v3.0.1

Changes include

  • Bugfix (non-breaking change that solves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking changes (change that is not backward-compatible and/or changes current functionality)

Checklist

  • I have tested this code
  • I have added unit test to cover this code
  • I have updated the documentation (README.md and /docs)
  • I have followed the contributing guide

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@coveralls
Copy link

coveralls commented May 31, 2022 •
edited
Loading

Coverage Status

Coverage remained the same at 94.169% when pulling 715561c on bump-yaml into 5046996 on main.

@thomaspoignant thomaspoignant merged commit a7d56d3 into main May 31, 2022
@thomaspoignant thomaspoignant deleted the bump-yaml branch May 31, 2022 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@thomaspoignant @coveralls