🚀 gha: Bump peter-evans/create-pull-request from 4 to 5

[dependabot]

Bumps peter-evans/create-pull-request from 4 to 5.

Release notes

Sourced from peter-evans/create-pull-request's releases.

Create Pull Request v5.0.0

Behaviour changes

• The action will no longer leave the local repository checked out on the pull request branch. Instead, it will leave the repository checked out on the branch or commit that it was when the action started.
• When using add-paths, uncommitted changes will no longer be destroyed. They will be stashed and restored at the end of the action run.

What's new

• Adds input body-path, the path to a file containing the pull request body.
• At the end of the action run the local repository is now checked out on the branch or commit that it was when the action started.
• Any uncommitted tracked or untracked changes are now stashed and restored at the end of the action run. Currently, this can only occur when using the add-paths input, which allows for changes to not be committed. Previously, any uncommitted changes would be destroyed.
• The proxy implementation has been revised but is not expected to have any change in behaviour. It continues to support the standard environment variables http_proxy, https_proxy and no_proxy.
• Now sets the git safe.directory configuration for the local repository path. The configuration is removed when the action completes. Fixes issue peter-evans/create-pull-request#1170.
• Now determines the git directory path using the git rev-parse --git-dir command. This allows users with custom repository configurations to use the action.
• Improved handling of the team-reviewers input and associated errors.

News

🏆 create-pull-request won an award for "awesome action" at the Open Source Awards at GitHub Universe. Thank you for your support and for making create-pull-request one of the top used actions. Please give it a ⭐, or even buy me a coffee.

What's Changed

• v5 by @​peter-evans in peter-evans/create-pull-request#1792
• 15 dependency updates by @​dependabot

Full Changelog: peter-evans/create-pull-request@v4.2.4...v5.0.0

Create Pull Request v4.2.4

⚙️ Patches some recent security vulnerabilities.

What's Changed

• Update concepts-guidelines.md by @​chrisbruford in peter-evans/create-pull-request#1610
• 58 dependency updates by @​dependabot

New Contributors

• @​chrisbruford made their first contribution in peter-evans/create-pull-request#1610

Full Changelog: peter-evans/create-pull-request@v4.2.3...v4.2.4

Create Pull Request v4.2.3

What's Changed

• fix: add check for missing token input by @​peter-evans in peter-evans/create-pull-request#1324

Full Changelog: peter-evans/create-pull-request@v4.2.2...v4.2.3

Create Pull Request v4.2.2

What's Changed

• fix: support github server url for pushing to fork by @​peter-evans in peter-evans/create-pull-request#1318

... (truncated)

Commits

• 5b4a9f6 v5 (#1792)
• 1847e5d build(deps-dev): bump eslint from 8.36.0 to 8.37.0 (#1803)
• c246f7e build(deps-dev): bump @​typescript-eslint/parser from 5.57.0 to 5.57.1 (#1801)
• 2dd2b11 build(deps-dev): bump eslint-import-resolver-typescript (#1802)
• 05d5a3c build(deps-dev): bump @​types/node from 18.15.10 to 18.15.11 (#1800)
• 21479f2 build(deps-dev): bump ts-jest from 29.0.5 to 29.1.0 (#1799)
• 36a56da build(deps-dev): bump @​typescript-eslint/parser from 5.56.0 to 5.57.0 (#1768)
• b7f0c97 build(deps-dev): bump prettier from 2.8.6 to 2.8.7 (#1767)
• 6a62596 build(deps): bump peter-evans/enable-pull-request-automerge from 2 to 3 (#1766)
• d1ed29f build(deps-dev): bump @​types/node from 18.15.5 to 18.15.10 (#1765)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Here are some friendly prose warnings from write-good:

In ./CODE_OF_CONDUCT.md
=============
* Giving and gracefully accepting constructive feedback
             ^^^^^^^^^^
"gracefully" can weaken meaning on line 22 at column 13
-------------
sing on what is best not just for us as individuals, but for the overall
                         ^^^^
"just" can weaken meaning on line 25 at column 31
-------------
individuals, but for the overall
                         ^^^^^^^
"overall" is wordy or unneeded on line 25 at column 71
-------------
t which could reasonably be considered inappropriate in a
                         ^^^^^^^^^^^^^
"be considered" may be passive voice on line 36 at column 39
-------------
nacceptable behavior may be
                         ^^^^^^^^^^^
"be
reported" may be passive voice on line 61 at column 72
-------------
All complaints will be reviewed and investigated promptly and fairly.
                    ^^^^^^^^^^^
"be reviewed" may be passive voice on line 64 at column 20
-------------
eviewed and investigated promptly and fairly.
                         ^^^^^^^^
"promptly" can weaken meaning on line 64 at column 49
-------------
nvestigated promptly and fairly.
                         ^^^^^^
"fairly" is a weasel word and can weaken meaning on line 64 at column 62
-------------
All community leaders are obligated to respect the privacy and security of the
                      ^^^^^^^^^^^^^
"are obligated" may be passive voice on line 66 at column 22
-------------
te. A public apology may be requested.
                         ^^^^^^^^^^^^
"be requested" may be passive voice on line 81 at column 49
-------------
ing the Code of Conduct, is allowed during this period.
                         ^^^^^^^^^^
"is allowed" may be passive voice on line 103 at column 42
-------------
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
                     ^^^^^^^^^^
"is adapted" may be passive voice on line 117 at column 21
-------------
munity Impact Guidelines were inspired by
                         ^^^^^^^^^^^^^
"were inspired" may be passive voice on line 121 at column 28


In ./SECURITY.md
=============
ions of your project are currently being
                         ^^^^^^^^^
"currently" can weaken meaning on line 5 at column 73
-------------
ur project are currently being
                         ^^^^^^^^^^^^^^^
"being
supported" may be passive voice on line 5 at column 83
-------------
ect if the vulnerability is accepted or declined, etc.
                         ^^^^^^^^^^^
"is accepted" may be passive voice on line 20 at column 51


In ./README.md
=============
By default (without any additional options) this formula install the
                        ^^^^^^^^^^
"additional" is wordy or unneeded on line 20 at column 24
-------------
ehavior or add even more stuff.
                         ^^^^^
"stuff" can weaken meaning on line 22 at column 53
-------------
s all command line tools are installed.
                         ^^^^^^^^^^^^^
"are installed" may be passive voice on line 34 at column 61
-------------
*--HEAD** builds are not really supported. They may fail to install,
                         ^^^^^^
"really" can weaken meaning on line 36 at column 36
-------------
e Qt Installer Framework is located on [https://doc.qt.io/qtinstallerframework][
                         ^^^^^^^^^^
"is located" may be passive voice on line 44 at column 49
-------------
Many thanks to everyone reporting issues.
^^^^
"Many" is a weasel word and can weaken meaning on line 73 at column 0


In ./.github/PULL_REQUEST_TEMPLATE.md
=============
- [ ] Have you successfully run 'brew tests' with your changes locally?
               ^^^^^^^^^^^^
"successfully" can weaken meaning on line 5 at column 15


In ./docs/src/content/docs/en/introduction.md
=============
By default (without any additional options) this formula install the
                        ^^^^^^^^^^
"additional" is wordy or unneeded on line 19 at column 24
-------------
ehavior or add even more stuff.
                         ^^^^^
"stuff" can weaken meaning on line 21 at column 53
-------------
s all command line tools are installed.
                         ^^^^^^^^^^^^^
"are installed" may be passive voice on line 33 at column 61
-------------
*--HEAD** builds are not really supported. They may fail to install,
                         ^^^^^^
"really" can weaken meaning on line 35 at column 36
-------------
e Qt Installer Framework is located on [https://doc.qt.io/qtinstallerframework][
                         ^^^^^^^^^^
"is located" may be passive voice on line 43 at column 49


In ./docs/README.md
=============
All commands are run from the root of the project, from a terminal:
             ^^^^^^^
"are run" may be passive voice on line 30 at column 13
-------------
'src/config.ts' contains several data objects that describe metadata about your 
                         ^^^^^^^
"several" is a weasel word on line 51 at column 25
-------------
he theme's look and feel is controlled by a few key variables that you can custo
                         ^^^^^^^^^^^^^
"is controlled" may be passive voice on line 55 at column 26
-------------
 feel is controlled by a few key variables that you can customize yourself. You'
                         ^^^
"few" is a weasel word on line 55 at column 45
-------------
an customize the page in many different ways to optimize SEO and other things. F
                         ^^^^
"many" is a weasel word and can weaken meaning on line 71 at column 228
-------------
o optimize SEO and other things. For example, you can use the 'title' and 'descr
                         ^^^^^^
"things" can weaken meaning on line 71 at column 274
-------------
description: Really cool docs example that uses Astro
             ^^^^^^
"Really" can weaken meaning on line 76 at column 13
-------------
The sidebar navigation is controlled by the 'SIDEBAR' variable in your 'src/conf
                       ^^^^^^^^^^^^^
"is controlled" may be passive voice on line 87 at column 23
-------------
r navigation has already been created for you.
                         ^^^^^^^^^^^^
"been created" may be passive voice on line 87 at column 191
-------------
top-level 'en' key: This is needed for multi-language support. You can change it
                         ^^^^^^^^^
"is needed" may be passive voice on line 103 at column 34
-------------
### Multiple Languages support
    ^^^^^^^^
"Multiple" is wordy or unneeded on line 105 at column 4
-------------
o docs template supports multiple languages out of the box. The default theme on
                         ^^^^^^^^
"multiple" is wordy or unneeded on line 107 at column 33
-------------
e box. The default theme only shows 'en' documentation, but you can enable multi
                         ^^^^
"only" can weaken meaning on line 107 at column 86
-------------
he default language, you just need to modify the redirect path in 'src/pages/ind
                         ^^^^
"just" can weaken meaning on line 155 at column 56
-------------
nguage, you just need to modify the redirect path in 'src/pages/index.astro':
                         ^^^^^^
"modify" is wordy or unneeded on line 155 at column 69
-------------
 I don't plan to support multiple languages?
                         ^^^^^^^^
"multiple" is wordy or unneeded on line 166 at column 36
-------------
ts need (or can support) multiple languages. You can continue to use this theme 
                         ^^^^^^^^
"multiple" is wordy or unneeded on line 168 at column 60
-------------
 is not English, you can just replace 'en' in directory layouts and configuratio
                         ^^^^
"just" can weaken meaning on line 170 at column 48
-------------
ch.algolia.com/). If you are accepted to the DocSearch program, provide your API
                         ^^^^^^^^^^^^
"are accepted" may be passive voice on line 174 at column 151
-------------
 see where the component is added.
                         ^^^^^^^^
"is added" may be passive voice on line 178 at column 154

[github-actions]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
❌ COPYPASTE	jscpd	yes		2	1.32s
❌ CSS	scss-lint	5		5	2.72s
❌ CSS	stylelint	5	5	1	2.35s
❌ EDITORCONFIG	editorconfig-checker	88		1	0.28s
✅ JSON	eslint-plugin-jsonc	9	0	0	0.98s
✅ JSON	jsonlint	8		0	0.17s
⚠️ JSON	prettier	9	3	1	0.6s
✅ JSON	v8r	9		0	7.69s
⚠️ MARKDOWN	markdownlint	8	2	2	0.63s
✅ MARKDOWN	markdown-link-check	8		0	44.97s
✅ MARKDOWN	markdown-table-formatter	8	2	0	0.31s
❌ REPOSITORY	checkov	yes		2	12.34s
✅ REPOSITORY	gitleaks	yes		no	0.38s
✅ REPOSITORY	git_diff	yes		no	0.06s
❌ REPOSITORY	goodcheck	yes		1	1.34s
✅ REPOSITORY	secretlint	yes		no	1.29s
✅ REPOSITORY	trivy	yes		no	5.49s
❌ SPELL	cspell	96		34	6.55s
✅ SPELL	misspell	95	1	0	0.13s
⚠️ YAML	prettier	14	2	1	1.79s
❌ YAML	v8r	11		1	21.42s
✅ YAML	yamllint	14		0	1.49s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by