-
Notifications
You must be signed in to change notification settings - Fork 49
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
[BRE-224] Create a GitHub release workflows for sdk #1078
[BRE-224] Create a GitHub release workflows for sdk #1078
Conversation
…ub-Release-workflows-for-SDK
New Issues
Fixed Issues
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1078 +/- ##
=======================================
Coverage 58.31% 58.31%
=======================================
Files 192 192
Lines 13486 13486
=======================================
Hits 7865 7865
Misses 5621 5621 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
.github/workflows/publish-wasm.yml
Outdated
workflow: build-wasm.yml | ||
path: ${{ github.workspace }}/languages/js/wasm | ||
workflow_conclusion: success | ||
branch: ${{ inputs.release_type == 'Dry Run' && 'main' || github.ref_name }} |
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.
branch: ${{ inputs.release_type == 'Dry Run' && 'main' || github.ref_name }} | |
branch: main |
Is the Download artifacts
step being used, or the one below this for Download artifact
?
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.
The one below. Fixed it.
.github/workflows/publish-napi.yml
Outdated
npm_publish: | ||
description: "Publish to NPM registry" | ||
required: true | ||
default: true | ||
type: boolean |
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.
npm_publish: | |
description: "Publish to NPM registry" | |
required: true | |
default: true | |
type: boolean |
Since this workflow only publishes to NPM, we can remove the input. It would do nothing if the box was not checked.
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.
Removed.
.github/workflows/publish-napi.yml
Outdated
name: Publish NPM | ||
runs-on: ubuntu-22.04 | ||
needs: setup | ||
if: inputs.npm_publish |
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.
if: inputs.npm_publish |
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.
Removed.
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
…ttps://github.com/bitwarden/sdk into BRE-224-Create-a-GitHub-Release-workflows-for-SDK
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
Co-authored-by: Vince Grassia <[email protected]>
…ub-Release-workflows-for-SDK
…ttps://github.com/bitwarden/sdk into BRE-224-Create-a-GitHub-Release-workflows-for-SDK
🎟️ Tracking
https://bitwarden.atlassian.net/browse/BRE-224
📔 Objective
Create and/or split workflow to create a GitHub Release for SDK parts.
⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes