-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the shared GitHub Actions workflows for buildpack releases #156
Conversation
This sets up the release automation scripts from [languages-github-actions](https://github.com/heroku/languages-github-actions) for the Procfile buildpack. Also in this PR: * adds the target Docker repository to `buildpack.toml` to align with the metadata used by other Heroku buildpacks [W-13658758](https://gus.lightning.force.com/a07EE00001UkuZgYAJ)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocked on:
- addressing the comments here (which are pretty much the same as the ones on the Python CNB PR)
- having a few more of the issues reported at https://github.com/heroku/languages-github-actions/issues fixed first
...but I'm very much looking forward to this landing! :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, thank you! 😄
@colincasey Ah, I've just noticed that the current README for this repo has deployment instructions which will be outdated when this merges: I guess that section can be replaced with a link to these new docs instead? eg similar to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
We can remove these separated workflows now that the following PRs have been merged: - heroku/buildpacks-jvm#554 - heroku/buildpacks-php#14 - heroku/buildpacks-go#123 - heroku/buildpacks-ruby#183 - heroku/buildpacks-nodejs#609 - heroku/buildpacks-python#58 - heroku/buildpacks-procfile#156
We can remove this fallback key for reading the repository to publish to now that the following PRs have been merged: - heroku/buildpacks-go#124 - heroku/buildpacks-php#15 - heroku/buildpacks-ruby#184 - heroku/buildpacks-jvm#555 - heroku/buildpacks-nodejs#610 - heroku/buildpacks-python#58 - heroku/buildpacks-procfile#156
We can remove this fallback key for reading the repository to publish to now that the following PRs have been merged: - heroku/buildpacks-go#124 - heroku/buildpacks-php#15 - heroku/buildpacks-ruby#184 - heroku/buildpacks-jvm#555 - heroku/buildpacks-nodejs#610 - heroku/buildpacks-python#58 - heroku/buildpacks-procfile#156
* Post PR #91 Cleanup We can remove these separated workflows now that the following PRs have been merged: - heroku/buildpacks-jvm#554 - heroku/buildpacks-php#14 - heroku/buildpacks-go#123 - heroku/buildpacks-ruby#183 - heroku/buildpacks-nodejs#609 - heroku/buildpacks-python#58 - heroku/buildpacks-procfile#156 * PR feedback
This sets up the release automation scripts from languages-github-actions for the Procfile buildpack.
Also in this PR:
buildpack.toml
to align with the metadata used by other Heroku buildpacksW-13658758