You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should only publish them as a Tag on GitHub, not a release. That way we don't flood people who are subscribed to the repo.
Do people get notified by pre-releases? I think we have to present a changelog somewhere, otherwise people won't know what has changed since the previous release and what's there to be played with. I would have thought of GitHub releases for this.
We should discuss whether we want these to go to both DockerHub and NPM, or just NPM 🤔
Personally, I'd like to deploy to both, whereas DockerHub seems almost more important to me, so that people can try out a nightly release easily without having to setup Node.js, etc.
I think we have to present a changelog somewhere, otherwise people won't know what has changed since the previous release and what's there to be played with. I would have thought of GitHub releases for this.
Are you thinking this would be a changelog since the last 24h release, or a changelog since the last public version?
Ideally it'll auto-publish based based on the changesets with a version suffix
{version}-nightly.{date}
, for examplev12.6.1-nightly.20240306
.I think we should only publish them as a Tag on GitHub, not a release. That way we don't flood people who are subscribed to the repo.
The text was updated successfully, but these errors were encountered: