Update JamesIves/github-pages-deploy-action action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
JamesIves/github-pages-deploy-action	action	major	3.7.1 -> v4.3.3

---

Release Notes

JamesIves/github-pages-deploy-action

v4.3.3

Compare Source

Changes

• Resolves an issue in some workflows that were caused by a recent change to permission handling.

v4.3.2

Compare Source

Changes

• Resolves an issue with folder permissions that causes an issue in container workflows when rsync attempts to run.

v4.3.1

Compare Source

Changes

• Resolves an issue caused by Git 2.36 when running the action within a container.
  • The working directory is now added to the safe.directory global directory.
  • Integration tests have been updated so one of the samples run in a Docker container so this gets picked up by integration tests in the future.

v4.3.0

Compare Source

Changes

• Implements a new option available behind a flag, force. If set to false the action will no longer force push, instead attempting 3 times to resolve rejected commits when making parallel/subsequent deployments. In a future version false will be set as the default. Massive thanks to @​rossjrw for this feature addition.
• Modified the Node version which the action is developed/tested against from 14 to 16.

Minor Changes

• Third-party dependency updates.
• Test coverage improvements.

v4.2.5

Compare Source

Minor Changes

• Corrects an issue in the publishing pipeline that was causing workflow failures.

v4.2.4

Compare Source

Minor Changes

• Modified how workflow notices get displayed. (#​1033 Thanks to @​hemberger)
• Dependency upgrades.

v4.2.3

Compare Source

Minor Changes

• Improved action logging. This is part 1 or 2 updates that will make the logs easier to traverse. Warnings and notices are now provided so you don't need to expand the logs to get the termination message.
• Dependency bumps across the board.

v4.2.2

Compare Source

Minor Changes

• Introduces major version tags. You can now point your workflow to JamesIves/github-pages-deploy-action@v4 if you'd like to always have the most cutting edge changes outside of using the release branch directly.
• The version tags for this project now include a v to be consistent with other officially provided actions by GitHub. You can use JamesIves/github-pages-deploy-action@v4.2.2 for instance. Dependabot should pick up this change automatically.

v4.2.1

Compare Source

Minor Changes

• Resolves an issue where the operating system warning was showing incorrectly.

v4.2.0

Compare Source

Happy New Year 2022!

Minor Changes

• Implements a warning if you're using an unsupported operating system. This will occur if the workflow runs within MacOS or Windows. The workflow will not be cancelled.
• The action is now case insensitive, allowing you to make casing changes to files so long as you commit them using the git mv command prior to the workflow running. (#​895)
• Fixes an issue that was causing single-commit to fail when using repository-name if the branch name was equal from the origin to destination. (#​665)
• Enabled Dependabot updates for the GitHub Actions that are used as part of the projects integration tests.
• Made improvements to the issue template.
• Modified the dev container so it now properly runs on Node 14 when used within GitHub Codespaces.
• Modified the default exclude list to use an enum value to ensure accuracy.
• Dependency upgrades.

v4.1.9

Compare Source

Minor Changes

• Dependency/security updates from third parties.

v4.1.8

Compare Source

Minor Changes

• Library dependency and security bumps.
• README modifications.

New Contributors

• @​anushbhatia made their first contribution in Modified the link & linked security documentation JamesIves/github-pages-deploy-action#924

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

v4.1.7

Compare Source

Minor Changes

• Dependency upgrades
• Modified README examples to use npm ci instead of npm install in examples by @​bananer in use "npm ci" instead of "npm install" in examples 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 use "npm ci" instead of "npm install" in examples JamesIves/github-pages-deploy-action#934

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

v4.1.6

Compare Source

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

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: ''

v4.1.5

Compare Source

Minor Changes

• Resolves a bug that was causing the usage of the clean and single commit options together to fail.
• Numerous dependency and security bumps.

v4.1.4

Compare Source

Minor Changes

• Resolves an issue with the buffer length causing issues with very large repos (thanks to @​garazdawi)
• Lots of dependency updates across the board.
• Minor README adjustments.

v4.1.3

Compare Source

Minor Changes

• Resolves a false positive error that was caused by a build cleanup step.

v4.1.2

Compare Source

Minor Changes

• Fixed an issue that prevented you from deploying if you had a similarly named branch, ie docs and ci/docs.
• Resolved an issue that prevents you from deploying a second time in the same workflow job. The action will now correctly cleanup branch artifacts after it's done deploying.
• Standardized ESLint configuration, now using typescript-eslint as opposed to the GitHub configuration.
• Documentation change/cleanup for some parts.
• Added sponsorship automation for people who donate via GitHub Sponsors.

v4.1.1

Compare Source

Minor Changes

• Dependency/security updates provided through Dependabot.
• Minor tooling changes, format is now lint:format for consistency.
• Removed ^ keyword in all dependencies within package.json.

v4.1.0

Compare Source

Major Changes

• This action now supports self-hosted GitHub instances such as GitHub Enterprise. The GitHub Actions runner passes down the server url of the GitHub instance it's running on which is what the deployment step will use going forward to determine where it needs to make requests to. If you have any issues with this feature please create an issue. For more details about how to use an open source action on GitHub Enterprise please refer to the official GitHub documentation.

Minor Changes

• Dependency updates across the board.

v4.0.0

Compare Source

🎉 Version 4 is here! Please refer to the migration guide for information on breaking changes if you were previously using version 3. 🎉

Major Changes ⚡

• All inputs should are now kebab case/lowercase as opposed to snake case.
• GITHUB_TOKEN is no longer required, if you rely on the default authentication method you can simply remove this field.
• If you rely on an ACCESS_TOKEN to make your deployments you now need to use the token input. Please refer to the migration guide for more information.
• SSH is now ssh-key and can accept either true or a private SSH key. Please refer to the README or/and migration guide for more details about how this works in this version.
• The LFS option is now deprecated.
• The PRESERVE option is no longer needed and is now deprecated.
• CLEAN_EXCLUDE has a different syntax, please refer to the README or/and migration guide for more details.
• Integration tests now run on every pull request.

Minor Changes 📜

• You can now use the dry-run input to verify compatibility in your workflow without pushing to the branch. Check out the README for additional details.
• ESlint is now enabled for unit tests.
• CodeQL is now enabled on all incoming pull requests.
• Release branch based dependencies are now automatically generated on a commit to a releases/* branch using GitHub Actions.
• Integration tests now point to version 4.
• Security documentation has been updated.
• GitHub Codespaces support has been enabled for the project.
• You no longer need to set preserve-credentials: false on the actions/checkout step. The deployment step will now appropriately discard the baked configuration before making its deployment.
• Updated logo/meta image provided by Paganini.

Special Thanks 💖

Massive thank you to @​Pike for all of their contributions to version 4. This release would not have been possible if it wasn't for them.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
kakeibooo	🛑 Canceled (Inspect)		May 9, 2022 at 2:58PM (UTC)