Please use cf-buildpack-update-action in place of this. This repository will be archived soon. Existing GitHub Action workflows using this repo here might break.
Create pull requests to update Cloud Foundry buildpacks in manifest files.
Aiming for reproducible deployments it's a necessary step to pin a buildpack in a project to a specific version in the Cloud Foundry manifest, so it will always use the one you specify.
The disadvantage of pinning is that any improvement in a newer version is not automatically taken over to the project.
With this GitHub action a pull request will be created if there is a newer version of a buildpack available. That way the project can stay up-to-date but with a conscious and deliberate change, traceable in version control.
Create a file in your repo called .github/workflows/buildpack-update.yml and in it put this code (remember to update 'your-team-email-address@springernature.com' to one that is correct for your team)
on:
schedule:
- cron: '0 4 * * 1-5' # Every workday at 0500 UTC
workflow_dispatch:
jobs:
buildpack_updates_job:
runs-on: ee-runner
name: buildpack updates
steps:
- name: Check out the repo
uses: actions/checkout@v2
- name: run buildpack-update-action
uses: springernature/buildpack-update-action@v1.0.2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
AUTHOR_EMAIL: your-team-email-address@springernature.com
AUTHOR_NAME: Buildpack Update Action
This should be picked up automatically in Github as a new Action and produce a PR (Pull Request) with the buildpack version changes whenever a new version is available. Just accept and merge the PR and you will be up to date.
Before submitting any pull requests, please ensure that you have adhered to the contribution guidelines.
- enhance documentation
- have an automated release process?
- improve build time
- make it configurable, see Dependabot config for ideas
Copyright Springer Nature