Releases: enriikke/gatsby-gh-pages-action
Bump to Node 16
Node 12 is no longer supported by GitHub Actions (rightfully so!) so this release simply bumps it to Node 16 plus updates other dependencies.
Custom Deploy User Support
This release includes a new feature that allows you to specify a deployment user for your commits! 🎉
You can do this by passing git-config-name and git-config-email as inputs:
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- uses: enriikke/gatsby-gh-pages-action@v2
with:
access-token: ${{ secrets.ACCESS_TOKEN }}
git-config-name: DeployBot
git-config-email: deploybot@mycompany.com
It also includes a vulnerability fix: #62
And moves away from yarn
into npm
for local development.
Bump major and minor release tags to include latest features.
This release includes a security vulnerability fix as well as correctly bumps the major and minor tag versions. 🎉 😃
Fixes compatibility with NPM
This release fixes an issue running this Action with NPM. Instead of running gatsby build
directly, it will use the build
script defined in package.json
. ✌️
Persist CNAME between builds
With this release, you to add a CNAME
file at the root of the project containing the custom domain you would like to use and Gatsby Publish will copy it over when deploying so your domain is persisted between builds.
Migrate to JavaScript Action
Migrates to a new JavaScript Action and makes use of the new way of defining inputs for an Action, rather than relying on environment variables alone. The documentation is also updated to align with GitHub Pages requirements better. 🎉 🚀
Gatsby Publish Action on Marketplace
Update default DEPLOY_BRANCH
to master
since User and Org pages are required to use it. Project pages can still set DEPLOY_BRANCH
to whatever they use. 🎉
Gatsby Publish Action on Marketplace
Publish the first iteration of this Action on the Marketplace! 🎉