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.

Minor Changes

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

Minor Changes

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

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.

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/[email protected] for instance. Dependabot should pick up this change automatically.

Minor Changes

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

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.

Minor Changes

• Dependency/security updates from third parties.

Minor Changes

• Library dependency and security bumps.
• README modifications.

New Contributors

• @anushbhatia made their first contribution in https://github.com/JamesIves/github-pages-deploy-action/pull/924

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/4.1.7...4.1.8

Minor Changes

• Dependency upgrades
• Modified README examples to use npm ci instead of npm install in examples by @bananer in https://github.com/JamesIves/github-pages-deploy-action/pull/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/[email protected]

      - name: Install and Build 🔧
        run: |
          npm install
          npm run build

      - name: Deploy 🚀
        uses: JamesIves/[email protected]
        with:
          branch: gh-pages
          folder: build
          git-config-email: <>

New Contributors

• @bananer made their first contribution in https://github.com/JamesIves/github-pages-deploy-action/pull/934

Full Changelog: https://github.com/JamesIves/github-pages-deploy-action/compare/4.1.6...4.1.7