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

Merged
merged 1 commit into from
Jul 31, 2024
Merged

release: v0.54.0 [main] #7075

merged 1 commit into from
Jul 31, 2024

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-30)

Features

Bug Fixes

  • Add dependencyManagement exclusions to the child exclusions (#6969) (dc68a66)
  • add missing platform and type to spec (#7149) (c8a7abd)
  • cli: error on missing config file (#7154) (7fa5e7d)
  • close file when failed to open gzip (#7164) (2a577a7)
  • dotnet: don't include non-runtime libraries into report for *.deps.json files (#7039) (5bc662b)
  • dotnet: show nuget package dir not found log only when checking nuget packages (#7194) (d76feba)
  • ignore nodes when listing permission is not allowed (#7107) (25f8143)
  • java: avoid panic if deps from pom in it dir are not found (#7245) (4e54a7e)
  • java: use go-mvn-version to remove Package duplicates (#7088) (a7a304d)
  • misconf: do not evaluate TF when a load error occurs (#7109) (f27c236)
  • nodejs: detect direct dependencies when using latest version for files yarn.lock + package.json (#7110) (54bb8bd)
  • report: hide empty table when all secrets/license/misconfigs are ignored (#7171) (c3036de)
  • secret: skip regular strings contain secret patterns (#7182) (174b1e3)
  • secret: trim excessively long lines (#7192) (92b13be)
  • secret: update length of hugging-face-access-token (#7216) (8c87194)
  • server: pass license categories to options (#7203) (9d52018)

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 4 times, most recently from 93e1823 to f666ad4 Compare July 16, 2024 05:39
@aqua-bot aqua-bot force-pushed the release-please--branches--main branch from f666ad4 to fba3a67 Compare July 22, 2024 04:07
@knqyf263
Copy link
Collaborator

@simar7 will be leading this release.
#6809 (comment)

@aqua-bot aqua-bot force-pushed the release-please--branches--main branch 14 times, most recently from fa274f6 to 12dfae2 Compare July 29, 2024 06:40
@DmitriyLewen
Copy link
Contributor

@aquasecurity/trivy I created #7248
You can write your own work.

@aqua-bot aqua-bot force-pushed the release-please--branches--main branch 3 times, most recently from 016517f to 1769961 Compare July 30, 2024 07:23
@aqua-bot aqua-bot force-pushed the release-please--branches--main branch from 1769961 to b915697 Compare July 30, 2024 08:25
Copy link
Collaborator

@knqyf263 knqyf263 left a comment

Choose a reason for hiding this comment

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

I've written release notes.

@DmitriyLewen DmitriyLewen added this pull request to the merge queue Jul 31, 2024
Merged via the queue into main with commit ff403a3 Jul 31, 2024
11 checks passed
@DmitriyLewen DmitriyLewen deleted the release-please--branches--main branch July 31, 2024 06:00
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.

5 participants