feat(release.yml): Add a (3 jobs)-based GHA using release-please #434
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
erikmd
added
kind: feature
Closed
15 tasks
erikmd
force-pushed
the
use-release-please
branch
5 times, most recently
from
a0cdaa1
to
059aea9
Compare
* Use var OPAM_RELEASE (GitHub PAC) * Use "expect" to workaround the lack of this feature: ocaml-opam/opam-publish#132 Co-Authored-By: Yann Régis-Gianas <yann@regis-gianas.org> Co-Authored-By: Erik Martin-Dorel <erik@martin-dorel.org>
erikmd
force-pushed
the
use-release-please
branch
from
059aea9
to
e4556e7
Compare
|
FYI @yurug, all details of the whole workflow |
This was referenced Oct 6, 2021
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.
Use var
OPAM_RELEASE(GitHub PAC) with the @proofbot accountUse
expectto workaround the factFeature wish: Add a
--yesflag to automatically accept Confirm questions ocaml-opam/opam-publish#132is not yet available.
This PR is the very last touch needed to prepare/automate 0.13.0 and upcoming releases:
git commit --allow-empty -m "chore: release 0.13.0" -m "Release-As: 0.13.0" && git push(in master)
opam-publish@yurug I plan to merge/use this PR soon; feel free to have a look if you can/want (anyway, I'll double-check the outcome "in pre-prod" beforehand with the dummy project we created)