Skip to content

Releases: JamesIves/github-pages-deploy-action

v4.2.4

16 Feb 13:46
2636389
Compare
Choose a tag to compare

Minor Changes

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

v4.2.3

31 Jan 13:18
Compare
Choose a tag to compare

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

10 Jan 13:35
Compare
Choose a tag to compare

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.

4.2.1

09 Jan 16:13
Compare
Choose a tag to compare

Minor Changes

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

4.2.0

06 Jan 15:32
Compare
Choose a tag to compare

Happy New Year 2022!

London

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.

4.1.9

05 Jan 17:10
Compare
Choose a tag to compare

Minor Changes

  • Dependency/security updates from third parties.

4.1.8

18 Dec 15:44
Compare
Choose a tag to compare

Minor Changes

  • Library dependency and security bumps.
  • README modifications.

New Contributors

Full Changelog: 4.1.7...4.1.8

4.1.7

26 Nov 13:19
Compare
Choose a tag to compare

Minor Changes

  • Dependency upgrades
  • Modified README examples to use npm ci instead of npm install in examples by @bananer in #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

Full Changelog: 4.1.6...4.1.7

4.1.6

18 Nov 13:52
60b5e92
Compare
Choose a tag to compare

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

4.1.5

26 Aug 14:13
Compare
Choose a tag to compare

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.