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

release: v0.54.0 [main] #7075

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

aqua-bot
Copy link
Contributor

@aqua-bot aqua-bot commented Jul 2, 2024

🤖 I have created a release beep boop

0.54.0 (2024-07-16)

Features

  • add log.FilePath() function for logger (#7080) (1f5f348)
  • add openSUSE tumbleweed detection and scanning (#6965) (17b5dbf)
  • cli: rename --vuln-type flag to --pkg-types flag (#7104) (7cbdb0a)
  • misconf: enabled China configuration for ACRs (#7156) (d1ec89d)
  • nodejs: add license parser to pnpm analyser (#7036) (03ac93d)

Bug Fixes

  • Add dependencyManagement exclusions to the child exclusions (#6969) (dc68a66)
  • add missing platform and type to spec (#7149) (c8a7abd)
  • close file when failed to open gzip (#7164) (2a577a7)
  • ignore nodes when listing permission is not allowed (#7107) (25f8143)
  • java: use go-mvn-version to remove Package duplicates (#7088) (a7a304d)
  • misconf: do not evaluate TF when a load error occurs (#7109) (f27c236)

Performance Improvements

  • debian: use bytes.Index in emptyLineSplit to cut allocation (#7065) (acbec05)

This PR was generated with Release Please. See documentation.

@DmitriyLewen
Copy link
Contributor

DmitriyLewen commented Jul 2, 2024

@knqyf263 it should be v0.54.0, no?

@knqyf263
Copy link
Collaborator

knqyf263 commented Jul 2, 2024

Release Please automatically determines the next version based on the commit prefixes. When feat commits are added to the main branch, it will be changed to v0.54.0. It currently has a performance change only.

@DmitriyLewen
Copy link
Contributor

thank you for explaining, otherwise I was starting to worry 😄

@aqua-bot aqua-bot changed the title release: v0.53.1 [main] release: v0.54.0 [main] Jul 2, 2024
@aqua-bot aqua-bot force-pushed the release-please--branches--main branch from 37e3898 to 29eb307 Compare July 2, 2024 10:08
@knqyf263
Copy link
Collaborator

knqyf263 commented Jul 2, 2024

It's v0.54.0 now, although #7080 should have been refactor as it doesn't affect users.

@DmitriyLewen
Copy link
Contributor

Yeah. It was my mistake.
Interesting - if i change description of #7080 now, will please release change description of this PR next time we push to the main branch or not?

@knqyf263
Copy link
Collaborator

knqyf263 commented Jul 2, 2024

Release Please sees a commit message. You need to amend the commit message in the main branch and force-push it.

@DmitriyLewen
Copy link
Contributor

oh...
force-push, especially for main branch, is a dangerous command.
I better double check type when i create a PR...

@knqyf263
Copy link
Collaborator

knqyf263 commented Jul 3, 2024

force-push, especially for main branch, is a dangerous command.

Actually, our branch protection doesn't allow it. It means you cannot change the type once you merge a PR.

@DmitriyLewen
Copy link
Contributor

Yeah. I understood you. Thank you for the clarification!

@aqua-bot aqua-bot force-pushed the release-please--branches--main branch 9 times, most recently from b3cbfd4 to 8f6c516 Compare July 10, 2024 03:25
@aqua-bot aqua-bot force-pushed the release-please--branches--main branch 3 times, most recently from a7f876d to 93e1823 Compare July 16, 2024 03:25
@aqua-bot aqua-bot force-pushed the release-please--branches--main branch from 93e1823 to f666ad4 Compare July 16, 2024 05:39
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.

None yet

3 participants