Bump actions/configure-pages from 3 to 4

[dependabot]

Bumps actions/configure-pages from 3 to 4.

Release notes

Sourced from actions/configure-pages's releases.

v4.0.0

Changelog

• Use a centralized .node-version file @​JamesMGreene (#117)
• Update action to node20 @​takost (#108)

See details of all code changes since previous release.

v3.0.7

Changelog

• Update Actions workflows to use Node 20.x @​JamesMGreene (#116)
• Bump eslint-plugin-github from 4.7.0 to 4.10.1 @​dependabot (#114)
• Bump word-wrap from 1.2.3 to 1.2.5 @​dependabot (#113)
• Bump jest from 29.5.0 to 29.7.0 @​dependabot (#112)
• Bump @​babel/traverse from 7.21.3 to 7.23.5 @​dependabot (#110)
• Bump espree from 9.5.2 to 9.6.1 @​dependabot (#111)
• Bump eslint from 8.38.0 to 8.40.0 @​dependabot (#93)

See details of all code changes since previous release.

v3.0.6

Changelog

• Bump eslint from 8.36.0 to 8.38.0 @​dependabot (#89)
• Bump eslint-plugin-github from 4.6.1 to 4.7.0 @​dependabot (#86)
• Bump eslint-config-prettier from 8.7.0 to 8.8.0 @​dependabot (#85)
• Bump prettier from 2.8.6 to 2.8.7 @​dependabot (#84)
• Make "Get Pages failed" error message more helpful @​WofWca (#83)
• Bump prettier from 2.8.4 to 2.8.6 @​dependabot (#81)
• Add a CodeQL security scanning workflow @​JamesMGreene (#68)

See details of all code changes since previous release.

v3.0.5

Changelog

• Bump jest from 29.4.3 to 29.5.0 @​dependabot (#77)
• Bump eslint from 8.35.0 to 8.36.0 @​dependabot (#76)
• Bump espree from 9.4.1 to 9.5.0 @​dependabot (#78)
• Bump eslint-config-prettier from 8.6.0 to 8.7.0 @​dependabot (#75)
• Bump eslint from 8.34.0 to 8.35.0 @​dependabot (#73)
• Bump jest from 29.4.1 to 29.4.3 @​dependabot (#72)
• Bump eslint-plugin-github from 4.6.0 to 4.6.1 @​dependabot (#71)
• Amend token coverage for enablement in Action metadata file @​JamesMGreene (#51)

See details of all code changes since previous release.

v3.0.4

Changelog

... (truncated)

Commits

• 1f0c5cd Merge pull request #117 from actions/use-node-version-file
• 591bb0d Merge branch 'main' into use-node-version-file
• 1465f01 Merge pull request #108 from takost/update-to-node-20
• f2fc553 Merge branch 'main' into update-to-node-20
• 373694e Use a centralized .node-version file
• 3a01413 Update action to node20
• See full diff 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)

[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.

[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.