Releases: JamesIves/github-pages-deploy-action
Releases · JamesIves/github-pages-deploy-action
v4.2.5
Minor Changes
- Corrects an issue in the publishing pipeline that was causing workflow failures.
v4.2.4
Minor Changes
- Modified how workflow notices get displayed. (#1033 Thanks to @hemberger)
- Dependency upgrades.
v4.2.3
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
Minor Changes
- Introduces major version tags. You can now point your workflow to
JamesIves/github-pages-deploy-action@v4if 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
vto be consistent with other officially provided actions by GitHub. You can useJamesIves/[email protected]for instance. Dependabot should pick up this change automatically.
4.2.1
Minor Changes
- Resolves an issue where the operating system warning was showing incorrectly.
4.2.0
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 mvcommand prior to the workflow running. (#895) - Fixes an issue that was causing
single-committo fail when usingrepository-nameif 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
Minor Changes
- Dependency/security updates from third parties.
4.1.8
Minor Changes
- Library dependency and security bumps.
- README modifications.
New Contributors
- @anushbhatia made their first contribution in #924
Full Changelog: 4.1.7...4.1.8
4.1.7
Minor Changes
- Dependency upgrades
- Modified README examples to use
npm ciinstead ofnpm installin examples by @bananer in #934 - Modified the
git-config-emailoption 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 agit-config-emailparameter 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
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-emailoption 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 exampleAuthor 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: ''