Releases: JamesIves/github-pages-deploy-action
Releases · JamesIves/github-pages-deploy-action
3.5.8
Minor Changes
- Made a change that prevents the
CLEAN
option from ignoring.nojekyll
andCNAME
files. It will now selectivly ignore these files only if they don't exist in the deployment folder. This allows you to update and upload them if you're using this option while still preventing mismatches from nuking them in the deployment branch. The README has also been updated to let you know that you need to manually delete them from the deployment branch should the need arise. - Made a small adjustment to the icons in the init function.
- Added a note about dependency versions and Dependabot in the README. Also made the base example use a tagged version as this is more consistent than referencing the
releases/v3
branch directly. - Dependency updates for ESLint/Node Types etc.
3.5.7
Minor Changes
- Added an introduction message with links to the Getting Started Tutorial / FAQ/ Contributing Guide etc.
- Dependency updates.
3.5.6
Minor Changes
- With this release the output provided by the git process is no longer silenced by default. This is based on feedback as contextual messages that occur before failures ere being swallowed. If you'd like to silence the output you can now set
SILENT: true
on the action config instead. - Updated a number of dependencies and a few spots in the README.
3.5.5
Minor Changes
- Rolls back a previous change that checks to see if the folder arg exists. This change requires some more testing and will return in a future update.
3.5.4
Minor Changes
- Adds the
--checksum
flag to the rsync command. - Adds a check to see if the deployment directory exists when the action runs and provides a helpful error message if not instead of failing with a generic.
3.5.3
Minor Changes
- Resolves an issue that prevents subsequent deployments from failing if they run immediately after each other in the same workflow. The action will now correctly remove the generated subtree, it will also randomly assign a branch name for the local deployment to prevent conflicts.
- Changed the generated folder name for the deployment to match the name of the action to prevent any sort of confusion about where a folder came from during a workflow run.
3.5.2
Minor Changes
- Fixes a publishing pipeline with the GitHub Registry.
3.5.1
Minor Changes
- Version sync.
3.5.0
Major Changes
- Added an export called
DEPLOYMENT_STATUS
which indicates if the deployment was successful or not. The possible outcomes aresuccess
failed
andskipped
. This allows you to reference the output in your workflow after the deployment so you can do things such as posting the status to a third party service. You can read more here: https://github.com/JamesIves/github-pages-deploy-action#deployment-status
Minor Changes
- Plenty of dependency updates.
3.4.9
Minor Changes
- Resolves an issue that was preventing nested folders from being created with the
TARGET_FOLDER
option. - Made an update to the integration tests so they take nested folders into consideration.