{"id":19712384,"url":"https://github.com/springernature/cf-buildpack-update-action","last_synced_at":"2025-07-29T17:13:25.598Z","repository":{"id":38211344,"uuid":"457926876","full_name":"springernature/cf-buildpack-update-action","owner":"springernature","description":"A GitHub Action to allow you to scan projects for out-of-date Cloud Foundry buildpacks.","archived":false,"fork":false,"pushed_at":"2024-03-23T00:03:27.000Z","size":583,"stargazers_count":4,"open_issues_count":12,"forks_count":1,"subscribers_count":42,"default_branch":"main","last_synced_at":"2025-04-25T18:53:56.169Z","etag":null,"topics":["buildpack","cloudfoundry","github-actions"],"latest_commit_sha":null,"homepage":"","language":"Kotlin","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/springernature.png","metadata":{"files":{"readme":"README.md","changelog":"HISTORY.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS"}},"created_at":"2022-02-10T19:54:20.000Z","updated_at":"2025-02-17T20:26:13.000Z","dependencies_parsed_at":"2023-01-04T18:32:17.872Z","dependency_job_id":"22e383f1-9f50-451c-8d54-1c9755f64517","html_url":"https://github.com/springernature/cf-buildpack-update-action","commit_stats":{"total_commits":213,"total_committers":10,"mean_commits":21.3,"dds":0.6431924882629108,"last_synced_commit":"d5e83952cbc7b073e9b4f1095bef5cf635811933"},"previous_names":[],"tags_count":31,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/springernature%2Fcf-buildpack-update-action","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/springernature%2Fcf-buildpack-update-action/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/springernature%2Fcf-buildpack-update-action/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/springernature%2Fcf-buildpack-update-action/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/springernature","download_url":"https://codeload.github.com/springernature/cf-buildpack-update-action/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":251559767,"owners_count":21609070,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["buildpack","cloudfoundry","github-actions"],"created_at":"2024-11-11T22:16:55.510Z","updated_at":"2025-04-29T18:30:53.808Z","avatar_url":"https://github.com/springernature.png","language":"Kotlin","readme":"# Buildpack update action\n\nCreate pull requests to update Cloud Foundry buildpacks in manifest files.\n\n## Why?\n\nAiming for reproducible deployments it's a necessary step to pin a buildpack in a project to a specific version in the\nCloud Foundry manifest, so it will always use the one you specify.\n\nThe disadvantage of pinning is that any improvement in a newer version is not automatically taken over to the project.\n\nWith this GitHub action a pull request will be created if there is a newer version of a buildpack available. That way\nthe project can stay up-to-date but with a conscious and deliberate change, traceable in version control.\n\n## Example usage\n\nCreate 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)\n \n    name: buildpack-update\n    on:\n      schedule:\n        - cron: '0 4 * * 1-5' # Every workday at 04:00 UTC\n      workflow_dispatch:\n    \n    jobs:\n      buildpack_updates_job:\n        runs-on: ee-runner\n        timeout-minutes: 30\n        name: buildpack updates\n        steps:\n          - name: Check out the repo\n            uses: actions/checkout@v4\n          - name: run cf-buildpack-update-action\n            uses: springernature/cf-buildpack-update-action@v1.0.10\n            env:\n              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n              AUTHOR_EMAIL: your-team-email-address@springernature.com\n              AUTHOR_NAME: Buildpack Update Action\n              GITHUB_STEP_SUMMARY_ENABLED: true\n\nThis should be picked up automatically in GitHub as a new Action and produce a PR (Pull Request) with the buildpack\nversion changes whenever a new version is available.\nJust accept and merge the PR and you will be up-to-date.\n\n### GitHub token and running automated tests\nFrom GitHub [documentation](https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow):  \n*If you do want to trigger a workflow from within a workflow run, you can use a GitHub App installation access token or a personal access token instead of GITHUB_TOKEN to trigger events that require a token.*\nSo, if the opened PR should run some automated tests, you will need a PAT (Personal Access token) or a GitHub app installation access token instead of the normal GitHub token.\n\n### GitHub step summary\n\nWhen setting `GITHUB_STEP_SUMMARY_ENABLED` to `true` (default is `false`) a job summary is created, \nsee [example output](https://github.com/springernature/dpas/actions/runs/3691628035/attempts/1#summary-10080794385).\n\n## Keep *your* action up-to-date\n\nYou can configure dependabot to keep your action which uses `cf-buildpack-update-action` up-to-date for every new\nversion on `cf-buildpack-update-action`.\n\n[Enabling Dependabot version updates for actions — Keeping your actions up to date with Dependabot - GitHub Docs](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot#enabling-dependabot-version-updates-for-actions)\n\n\n\u003e **Enabling Dependabot version updates for actions**\n\u003e 1. Create a *dependabot.yml* configuration file. If you have already enabled Dependabot version updates for other\n     ecosystems or package managers, simply open the existing *dependabot.yml* file.\n\u003e 1. Specify `\"github-actions\"` as a `package-ecosystem` to monitor.\n\u003e 1. Set the `directory` to `\"/\"` to check for workflow files in `.github/workflows`.\n\u003e 1. Set a `schedule.interval` to specify how often to check for new versions.\n\u003e 1. Check the *dependabot.yml* configuration file in to the `.github` directory of the repository. If you have edited\n     an existing file, save your changes.\n\n## Development\n\nBefore submitting any pull requests, please ensure that you have adhered to the [contribution guidelines][contrib].\n\n## Roadmap\n\n* enhance documentation\n* have an automated release process?\n* improve build time\n* make it configurable,\n  see [Dependabot config](https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)\n  for ideas\n\n## License\n\n[GPL 3][license]\n\nCopyright Springer Nature\n\n[contrib]: CONTRIBUTING.md\n\n[history]: HISTORY.md\n\n[license]: LICENSE \n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspringernature%2Fcf-buildpack-update-action","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fspringernature%2Fcf-buildpack-update-action","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fspringernature%2Fcf-buildpack-update-action/lists"}