-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat(root): add GitHub Actions workflow for releasing packages #8484
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
Conversation
✅ Deploy Preview for dashboard-v2-novu-staging canceled.
|
|
@scopsy Hey, I did some research — we’ll still need to publish the tag and release manually. I’ll put together some documentation for it. The issue with publishing the release and tag through the action is that it would tag the older version, without including this change that’s currently not merged in next. |
scopsy
left a comment
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.
How are we going to test it out? Maybe doing a nightly release or something like this?
@scopsy testing is something needs to be done via nightly/alpha/beta. Before that I will need token as well |
|
Awesome, than it looks good on my end 💪 Let's just test it with a nightly after merged to make sure everything works as expected. Also for the nightly, does it uses npm --tag ? to make sure it's not published as the latest version |
- Introduced a new input parameter 'nightly' to the release workflow. - Implemented logic to set a nightly version and handle nightly releases for versioning, changelog generation, and package publishing. - Updated the publish step to tag nightly releases appropriately.
…q#8484) Co-authored-by: Dima Grossman <dima@grossman.io>
What changed? Why was the change needed?
This fixes NV-6034
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer