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 3.1.0 #176

Merged

Conversation

rjaegers
Copy link
Member

@rjaegers rjaegers commented Oct 19, 2023

🤖 I have created a release beep boop

3.1.0 (2023-10-31)

Features

Bug Fixes


This PR was generated with Release Please. See documentation.

@rjaegers rjaegers requested a review from a team as a code owner October 19, 2023 06:20
@github-actions
Copy link
Contributor

github-actions bot commented Oct 19, 2023

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 10 0 0.09s
✅ DOCKERFILE hadolint 1 0 0.39s
✅ JSON eslint-plugin-jsonc 7 0 0 6.6s
✅ JSON prettier 7 0 0 0.56s
✅ JSON v8r 7 0 4.19s
✅ MARKDOWN markdownlint 3 0 0 0.97s
✅ MARKDOWN markdown-link-check 3 0 4.91s
✅ MARKDOWN markdown-table-formatter 3 0 0 0.31s
✅ REPOSITORY checkov yes no 26.79s
✅ REPOSITORY dustilock yes no 0.29s
✅ REPOSITORY gitleaks yes no 0.21s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY grype yes no 14.41s
✅ REPOSITORY secretlint yes no 1.35s
✅ REPOSITORY syft yes no 0.22s
✅ REPOSITORY trivy yes no 9.3s
✅ REPOSITORY trivy-sbom yes no 2.67s
✅ REPOSITORY trufflehog yes no 4.54s
✅ SPELL lychee 31 0 4.09s
✅ YAML prettier 12 0 0 0.92s
✅ YAML v8r 12 0 8.8s
✅ YAML yamllint 12 0 0.36s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

@rjaegers rjaegers force-pushed the release-please--branches--main--components--amp-devcontainer branch 2 times, most recently from 95942e7 to a14308b Compare October 23, 2023 07:16
@github-actions
Copy link
Contributor

github-actions bot commented Oct 23, 2023

Test Results

15 tests  ±0   15 ✔️ ±0   13m 9s ⏱️ - 2m 21s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ±0 

Results for commit 4d3f8fc. ± Comparison against base commit 5cda3b8.

♻️ This comment has been updated with latest results.

@rjaegers rjaegers force-pushed the release-please--branches--main--components--amp-devcontainer branch 4 times, most recently from e90994a to 96104a6 Compare October 31, 2023 13:28
Copy link
Contributor

github-actions bot commented Oct 31, 2023

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Manifest Files

@rjaegers rjaegers force-pushed the release-please--branches--main--components--amp-devcontainer branch from 96104a6 to 4d3f8fc Compare October 31, 2023 16:21
@rjaegers rjaegers added this pull request to the merge queue Nov 2, 2023
Merged via the queue into main with commit b7af8f4 Nov 2, 2023
16 checks passed
@rjaegers rjaegers deleted the release-please--branches--main--components--amp-devcontainer branch November 2, 2023 16:01
Copy link
Contributor

github-actions bot commented Nov 2, 2023

Pull Request Report (#176)

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

Time related measures

Description Value
PR lead time (from creation to close of PR) 14.4 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 2 Days
Time to merge after last review 1.5 Hours

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 2.3 Hours
Total time spend in last status check run on PR 1.8 Hours

@rjaegers
Copy link
Member Author

rjaegers commented Nov 2, 2023

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