Releases: WalshyDev/cf-pages-await
Releases · WalshyDev/cf-pages-await
v1.3.1
What's Changed
- docs: fix
Envrionment
typo by @Cherry in #8 - Change
commitHash
to not required by @HandyHat in #14 - bugfix(api): Fix api reponse on build failure by @misnard in #18
New Contributors
- @Cherry made their first contribution in #8
- @HandyHat made their first contribution in #14
- @misnard made their first contribution in #18
Full Changelog: v1...v1.3.1
Initial release!
Version 1
You can now wait for your Cloudflare Pages builds to finish and do an action such as cache purging all within actions! :)
Usage
- name: Await CF Pages
uses: WalshyDev/cf-pages-await@v1
with:
accountEmail: ${{ secrets.CF_ACCOUNT_EMAIL }}
apiKey: ${{ secrets.CF_API_KEY }}
accountId: '4e599df4216133509abaac54b109a647'
project: 'example-pages-project'
Example
name: Deploy
on: push
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Wait for CF Pages
id: cf-pages
uses: WalshyDev/cf-pages-await@v1
with:
accountEmail: ${{ secrets.CF_ACCOUNT_EMAIL }}
apiKey: ${{ secrets.CF_API_KEY }}
accountId: '4e599df4216133509abaac54b109a647'
project: 'test'
- run: |
curl -X \
-H "X-Auth-Email: ${{ secrets.CF_ACCOUNT_EMAIL }}" \
-H "X-Auth-Key: ${{ secrets.CF_API_KEY }}" \
-H "Content-Type: application/json" \
--data '{"purge_everything":true}' \
https://api.cloudflare.com/client/v4/zones/8d0c8239f88f98a8cb82ec7bb29b8556/purge_cache
Outputs
id
- Deployment ID, example:50ff553c-da5d-4846-8188-25ae82a3bb7d
environment
- Envrionment for this deployment, eitherproduction
orpreview
url
- URL for this deploymentalias
- Alias URL (Will be the branch URL such asfix-issue.project.pages.dev
or be the deployment URL)success
- If the deployment was successful
v1.3.0 - Support API tokens!
Await a specific build (based on commit hash)
v1.1.0 - GitHub Deployments and bug fixes
What's Changed
- Fixed infinite run bug
- Fixed 504 issues when you have a lot of deployments
- Added GitHub deployments - see the README for more
- Make sure the latest Pages deployment is for the current commit (Closes #1)
Credits
- @Erisa - Finding an easy fix for the 504 timeout issue
- @GregBrimble - Idea and code for the GitHub Deployments
Full Changelog: v1...v1.1
v1.0.1
Improved error output for network failures or the CF API not returning a JSON