Releases: JamesIves/github-pages-deploy-action
Releases · JamesIves/github-pages-deploy-action
2.0.0
Going forward version 2.0.0 and above will fully support the new GitHub actions CICD/yaml workflow style. The action will still work with the former HCL style for now but it's no longer going to be actively supported as GitHub plans to deprecate it by September 30 2019.
You can learn about how to migrate your usage of this action to the new yaml format by reading the GitHub migration guide and the action README file here. The biggest change is that you now need to call the actions/checkout action prior to using this action.
Any issues can be reported here.
Major Changes
- Changes the README to use the CICD workflow instructions using the new
yamlformat.
1.1.3
1.1.2
Minor Changes
- Fixes an issue where the base branch would always be set to
master. Thanks to @jaiselrahman for the pull request.
1.1.1
1.1.0
Major Changes
- If you deploy via this action with a custom domain, Github will nuke the configuration for the domain as the CNAME file is no longer present in the gh-pages branch due to how the commits get processed. In order to solve this I've added an additional environment variable called
CNAMEwhich will add the domain record into the build directory prior to the deploy. This will maintain the GitHub configuration which will solve the issue of pages 404ing after the deploy.
1.0.9
1.0.8
Major Changes
- Removed the need to create the remote branch prior to deployment. The action will now automatically create it for you if it doesn't exist when you attempt to deploy.
- Updated the README file to reflect this.
Credits
Thanks to @lizafloyd for the review.