Releases: CleverCloud/clever-cloud-review-app
v1.1.1
Fixes bug that prevented custom domain input instead of the default generated one from GitHub variables.
v1.1.0
Conditional comments depending on the actions performed on the PR (deploy, update, delete).
v1.0.0
Automate the action to make it composite, to ease the integration into users repositories.
Use GitHub variable for app-name input
- Previous version: user had to manually input the
app-name
to set application name, application alias and review app domain. - This version: the workflow uses the repository name by default to automatically input the
app-name
value.
Variable used: ${{ github.event.pull_request.base.repo.name }}
Improved Security Update
Goal
Allow external contribution while limiting external user generated input in the script
Changes
Scripts don't use BRANCH_NAME
but github.event.number
(#PR, GitHub generated).
Security update
This release contains a general security update with the following:
- Sourcing secrets in the step memory instead of yaml templating in shell script
- Guide on how to generate throwaway
CLEVER_SECRET
andCLEVER_TOKEN
only for GitHub Actions
v0.2.0
PRs from forks can now trigger a review app deployment.
v0.1.0 - Initial Release
First release for Clever Cloud Review Apps GitHub Action.
This action uses clever-tools to deploy review apps every time a PR is opened, redeploys on changes and delete it on PR closing (merged or not).
It currently works with branches pushed on the same repository and not across forks.