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 are success failed and skipped. 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.

3.4.8

Minor Changes

• Back tracked on the chmod changes from yesterday and instead configured the action to use the rmRF function provided by the @actions/toolkit package.

3.4.7

Minor Changes

• The temporary deployment directory will now have its folder permissions changed prior to being deleted on teardown. This was causing issues in a few instances where the rm -rf command would error.
• If you include a custom commit message the commit sha will no longer be attached to the message at the end. The commit SHA will only be included with the default message.

3.4.6

Minor Changes

• More publishing pipeline fixes.