Skip to content

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

bpolania
Copy link
Collaborator

@bpolania bpolania commented Apr 4, 2025

Description

This PR fixes issues with the npm release flow

@@ -7,6 +7,10 @@ on:
type: string
required: true
description: "Tag version to be published"
last_tag:
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

Copy link
Collaborator

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?

Copy link
Collaborator Author

@bpolania bpolania Apr 16, 2025

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.

DracoLi
DracoLi previously approved these changes Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants