Skip to content

Releases: JamesIves/github-pages-deploy-action

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/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

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

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.

4.1.4

04 Jun 14:27
Compare
Choose a tag to compare

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.

4.1.3

11 May 23:25
Compare
Choose a tag to compare

Minor Changes

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

4.1.2

10 May 14:42
Compare
Choose a tag to compare

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.

4.1.1

04 Apr 17:00
Compare
Choose a tag to compare

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.

4.1.0

04 Mar 14:26
Compare
Choose a tag to compare

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.