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

chore(main): release 4.6.0 #325

Merged

Conversation

rjaegers
Copy link
Member

@rjaegers rjaegers commented Feb 26, 2024

🤖 I have created a release beep boop

4.6.0 (2024-02-29)

Features

  • Add tests for sanitizers (#320) (0ea39ba)
  • Automatically update vscode extensions (#332) (12381a6)
  • deps: Bump gcovr from 7.0 to 7.2 in /.devcontainer (#323) (1e52f39)

Bug Fixes

  • Move customizations.vscode.settings to the correct level (#329) (87af97f)

This PR was generated with Release Please. See documentation.

@rjaegers rjaegers requested a review from a team as a code owner February 26, 2024 10:13
Copy link
Contributor

github-actions bot commented Feb 26, 2024

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 14 0 0.03s
✅ DOCKERFILE hadolint 1 0 0.29s
✅ JSON eslint-plugin-jsonc 8 0 0 3.15s
✅ JSON prettier 8 0 0 0.45s
✅ JSON v8r 8 0 3.95s
✅ MARKDOWN markdownlint 8 0 0 1.06s
✅ MARKDOWN markdown-link-check 8 0 10.13s
✅ MARKDOWN markdown-table-formatter 8 0 0 0.29s
✅ REPOSITORY checkov yes no 14.82s
✅ REPOSITORY gitleaks yes no 0.15s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY grype yes no 11.48s
✅ REPOSITORY secretlint yes no 1.32s
✅ REPOSITORY trivy yes no 7.3s
✅ REPOSITORY trivy-sbom yes no 2.24s
✅ REPOSITORY trufflehog yes no 6.45s
✅ SPELL lychee 43 0 1.3s
✅ YAML prettier 17 0 0 1.11s
✅ YAML v8r 17 0 12.68s
✅ YAML yamllint 17 0 0.36s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

Copy link
Contributor

github-actions bot commented Feb 26, 2024

Test Results

20 tests  ±0   20 ✅ ±0   41s ⏱️ -1s
 1 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit c5e5fa9. ± Comparison against base commit 12381a6.

♻️ This comment has been updated with latest results.

@rjaegers rjaegers force-pushed the release-please--branches--main--components--amp-devcontainer branch 2 times, most recently from 899ac9a to 2f8b734 Compare February 27, 2024 07:52
Copy link
Contributor

github-actions bot commented Feb 27, 2024

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer:latest to ghcr.io/philips-software/amp-devcontainer@sha256:37a5d6c3067176200a14a28ed031b7dc7dc273beab99da3874e496f6f8922097

OS/Platform Previous Size Current Size Delta
linux/amd64 594.66M 594.70M 40.21K (+0.01%)
linux/arm64 571.86M 571.90M 40.12K (+0.01%)

@rjaegers rjaegers force-pushed the release-please--branches--main--components--amp-devcontainer branch from 4c26c0b to f488010 Compare February 28, 2024 08:36
@rjaegers rjaegers force-pushed the release-please--branches--main--components--amp-devcontainer branch from f488010 to c5e5fa9 Compare February 29, 2024 10:36
@rjaegers rjaegers enabled auto-merge February 29, 2024 10:38
@rjaegers rjaegers added this pull request to the merge queue Feb 29, 2024
Merged via the queue into main with commit be46e89 Feb 29, 2024
14 checks passed
@rjaegers rjaegers deleted the release-please--branches--main--components--amp-devcontainer branch February 29, 2024 11:07
@rjaegers
Copy link
Member Author

Copy link
Contributor

Pull Request Report (#325)

Static measures

Description Value
Number of added lines 15
Number of deleted lines 1
Number of changed files 2
Number of commits 1
Number of reviews 1
Number of comments (w/o review comments) 4
Number of reviews that contains a comment to resolve 0
Number of reviews that requested a change from the author 0
Number of reviews that approved the Pull Request 1
Get the total number of participants of a Pull Request 4

Time related measures

Description Value
PR lead time (from creation to close of PR) 3 Days
Time that was spend on the branch before the PR was created 0 Sec
Time that was spend on the branch before the PR was merged 30.8 Min
Time to merge after last review 46 Min

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 18.7 Min
Total time spend in last status check run on PR 13.3 Min

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.

2 participants