-
Notifications
You must be signed in to change notification settings - Fork 69
Package Release Workflow Fixes #503
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
base: main
Are you sure you want to change the base?
Conversation
@@ -7,6 +7,10 @@ on: | |||
type: string | |||
required: true | |||
description: "Tag version to be published" | |||
last_tag: |
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.
do we need this? we don't need the release log to be generated right?
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.
We are using Mike Penze's github action and it requires a value for the fromTag
input.
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.
since we are creating the release docs ourselves, do we still need this?
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.
That action is for releasing the npm package, I mean, I don't think it's related with the docs.
Description
This PR fixes issues with the
npm
release flow