Skip to content

Conversation

@karthik2804
Copy link
Collaborator

Adds action that publishes package to npm when a tag starting with v is pushed.

@ThorstenHans
Copy link
Contributor

@karthik2804 see my comment in #324 about generating docs

@karthik2804
Copy link
Collaborator Author

@ThorstenHans I like the idea of releasing docs per release but would prefer not to roll that into this PR as that will involve us having to generate and commit docs or push it to a package. I am happy to tackle that as a follow-up.


# Determine if the tag is a release candidate or not
- name: Determine npm tag
id: npm_tag
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: why the ID for this job but not for anything else?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It can be safely removed.

@karthik2804
Copy link
Collaborator Author

Closing this as we will need to work on a different action once we have v4 because each interface becomes modularized.

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.

3 participants