Bump actions/deploy-pages from 3 to 4

[dependabot]

Bumps actions/deploy-pages from 3 to 4.

Release notes

Sourced from actions/deploy-pages's releases.

v4.0.0

Changelog

• Deploy pages using artifact IDs @​konradpabjan (#251)
• This version requires the permission actions: read in the workflows which use it.

---

ℹ️ This version of actions/deploy-pages is ONLY compatible with artifacts uploaded by either:

• actions/upload-pages-artifact@v3 or newer
• actions/upload-artifact@v4 or newer.

See details of all code changes since previous release.

⚠️ For use with products other than GitHub.com, such as GitHub Enterprise Server, please consult the compatibility table.

v3.0.1

Changelog

• Bump eslint from 8.54.0 to 8.55.0 @​dependabot (#266)
• Bump nock from 13.3.8 to 13.4.0 @​dependabot (#267)
• Bump eslint-config-prettier from 9.0.0 to 9.1.0 @​dependabot (#268)
• Bump @​actions/core from 1.10.0 to 1.10.1 @​dependabot (#269)
• Bump @​actions/github from 5.1.1 to 6.0.0 @​dependabot (#261)
• Update compatibility table for v3 @​JamesMGreene (#270)

🧰 Maintenance

• chore/docs: update version, fix typos @​kbdharun (#272)

---

See details of all code changes since previous release.

⚠️ For use with products other than GitHub.com, such as GitHub Enterprise Server, please consult the compatibility table.

Commits

• 7a9bd94 Merge pull request #290 from actions/dependabot/npm_and_yarn/undici-6.2.1
• eee8a27 Update distributables after Dependabot 🤖
• b6e5c85 Bump undici from 6.0.1 to 6.2.1
• b8d2528 Merge pull request #282 from actions/dependabot/github_actions/github/codeql-...
• 53d1eac Bump github/codeql-action from 2 to 3
• 3f0ef9d Merge pull request #281 from actions/dependabot/github_actions/actions/upload...
• 8275104 Bump actions/upload-artifact from 3 to 4
• 9be9d73 Merge pull request #280 from actions/dependabot/npm_and_yarn/eslint-8.56.0
• d8afefa Bump eslint from 8.55.0 to 8.56.0
• 304d0b7 Merge pull request #277 from actions/dependabot/github_actions/actions/publis...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.yml : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[github-actions]

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

This is a brief, high-level summary of what to expect from this process.

The team begins to review your PR if you request them to or if your PR meets these conditions:

• It's not a draft PR.
• It doesn't have a WIP prefix in the title.
• It passes validation and build steps.
• It doesn't have any merge conflicts.
• You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the team is here to help! You don't need to submit a fully polished and finished draft; the team can help you get content ready for merge.

While reviewing your PR, the team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the team marks your PR as Approved and merges it. Once your PR's merged, it's included when the site rebuilds.