Bump JamesIves/github-pages-deploy-action from 4.1.5 to 4.1.8

[dependabot]

Bumps JamesIves/github-pages-deploy-action from 4.1.5 to 4.1.8.

Release notes

Sourced from JamesIves/github-pages-deploy-action's releases.

4.1.8

Minor Changes

• Library dependency and security bumps.
• README modifications.

New Contributors

• @​anushbhatia made their first contribution in JamesIves/github-pages-deploy-action#924

Full Changelog: JamesIves/github-pages-deploy-action@4.1.7...4.1.8

4.1.7

Minor Changes

• Dependency upgrades
• Modified README examples to use npm ci instead of npm install in examples by @​bananer in JamesIves/github-pages-deploy-action#934
• Modified the git-config-email option again. If you wish to omit this field entirely you must now provide <> in the field instead of an empty string. This is due to the fact that GitHub Actions defaults all undefined fields to an empty string, causing the default behavior to not work when you don't provide a git-config-email parameter at all. You can find an example of this below.

name: Build and Deploy
on: [push]
jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout 🛎️
        uses: actions/checkout@v2.3.1
  - name: Install and Build 🔧
    run: |
      npm install
      npm run build

name: Deploy 🚀
uses: JamesIves/github-pages-deploy-action@4.1.6
with:
branch: gh-pages
folder: build
git-config-email: <>

New Contributors

• @​bananer made their first contribution in JamesIves/github-pages-deploy-action#934

Full Changelog: JamesIves/github-pages-deploy-action@4.1.6...4.1.7

4.1.6

Minor Changes

• Resolves an issue that was causing a permission error on the cleanup job. This error was caused by other actions changing directory permissions that prevented a worktree removal step from executing correctly. #922
• Migrated the project to Node version 14 across all integration tests, nvm file, etc.
• Numerous third party dependency updates/fixes.
• The git-config-email option now accepts an empty string as a valid value in a workflow. This will allow the email part of the commit signature to empty, for example Author Name <>. You can find an example of how to utilize this below. #868

... (truncated)

Commits

• da91e73 Deploy Production Code for Commit 9749ca0243cb3686439b9308a9f739aee5e7c932 🚀
• 9749ca0 Merge branch 'dev' into releases/v4
• 7a71951 Update SECURITY.md
• 2bb15be Create .nojekyll
• 0f8e592 Bump @​types/node from 16.11.12 to 17.0.0 (#952)
• cdaa202 Bump jest-circus from 27.4.4 to 27.4.5 (#950)
• 6d8d028 Bump typescript from 4.5.3 to 4.5.4 (#949)
• 4085c3f Deploying to dev from @ JamesIves/github-pages-deploy-action@590878d41e22e84f...
• 590878d Bump jest-circus from 27.4.2 to 27.4.4 (#948)
• 87734a2 Bump typescript from 4.5.2 to 4.5.3 (#947)
• 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)