Use the new "Prepare release" GitHub Actions workflow #683
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We now have a new reusable GitHub Actions workflow for preparing a new classic buildpack release: https://github.com/heroku/languages-github-actions/blob/main/.github/workflows/_classic-buildpack-prepare-release.yml This workflow works the same as the CNB version, except it does not need any version bump input, since we only every increment classic buildpack versions by one. Should any custom file changes be required as part of the PHP classic buildpack release process in the future, a bash command/commands can be passed via the workflow's `custom_update_command` option. GUS-W-14905318.
edmorley
force-pushed
the
edmorley/prepare-release-workflow
branch
from
22d1ef7 to
824be9f
Compare
dzuelke
approved these changes
Feb 1, 2024
Merged
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
We now have a new reusable GitHub Actions workflow for preparing a new classic buildpack release: https://github.com/heroku/languages-github-actions/blob/main/.github/workflows/_classic-buildpack-prepare-release.yml This workflow works the same as the CNB version, except it does not need any version bump input, since we only every increment classic buildpack versions by one. Should any custom file changes be required as part of the PHP classic buildpack release process in the future, a bash command/commands can be passed via the workflow's `custom_update_command` option. GUS-W-14905318.
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
We now have a new reusable GitHub Actions workflow for preparing a new classic buildpack release: https://github.com/heroku/languages-github-actions/blob/main/.github/workflows/_classic-buildpack-prepare-release.yml This workflow works the same as the CNB version, except it does not need any version bump input, since we only every increment classic buildpack versions by one. Should any custom file changes be required as part of the PHP classic buildpack release process in the future, a bash command/commands can be passed via the workflow's `custom_update_command` option. GUS-W-14905318.
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
We now have a new reusable GitHub Actions workflow for preparing a new classic buildpack release: https://github.com/heroku/languages-github-actions/blob/main/.github/workflows/_classic-buildpack-prepare-release.yml This workflow works the same as the CNB version, except it does not need any version bump input, since we only every increment classic buildpack versions by one. Should any custom file changes be required as part of the PHP classic buildpack release process in the future, a bash command/commands can be passed via the workflow's `custom_update_command` option. GUS-W-14905318.
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
We now have a new reusable GitHub Actions workflow for preparing a new classic buildpack release: https://github.com/heroku/languages-github-actions/blob/main/.github/workflows/_classic-buildpack-prepare-release.yml This workflow works the same as the CNB version, except it does not need any version bump input, since we only every increment classic buildpack versions by one. Should any custom file changes be required as part of the PHP classic buildpack release process in the future, a bash command/commands can be passed via the workflow's `custom_update_command` option. GUS-W-14905318.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We now have a new reusable GitHub Actions workflow for preparing a new classic buildpack release:
https://github.com/heroku/languages-github-actions/blob/main/.github/workflows/_classic-buildpack-prepare-release.yml
This workflow works similarly to the CNB prepare release workflow, except it does not need any version bump input, since we only ever increment classic buildpack versions by one.
Should any custom file changes be required as part of the PHP classic buildpack release process in the future, a bash command/commands can be passed via the workflow's
custom_update_commandoption.This PR also depends upon #682 landing first, so that the changelog is compatible with the workflow's version replacement regexes.
GUS-W-14905318.