-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
feat(actions): switch to GitHub action for releases #2458
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2458 +/- ##
=======================================
Coverage 85.43% 85.43%
=======================================
Files 11 11
Lines 1723 1723
Branches 99 99
=======================================
Hits 1472 1472
Misses 251 251 Continue to review full report at Codecov.
|
.github/workflows/release.yaml
Outdated
const latestRelease = await github.issues.addLabels({ | ||
owner, | ||
repo, | ||
issue_number: ${{steps.release-please.outputs.pr}}, |
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.
Is the step called release-pr
, not release-please
?
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.
(I have no idea actually :) )
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.
No, good catch, I believe it should be release-pr
.
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.
Let's see how it works :)
This moves us to using a GitHub action for running release-please and publishing to npm, this will make it easier for us to have two release flows in the repo:
googleapis
.src/apis
.TODO: