ci(): publish @next version on PR merge

[ShaMan123]

@asturur What do you think about adding a ci job that will build dist and publish to npm a @next tag after every PR merge?
I think it will be used and is a good devX addition.
I patch fabric manually when a major PR is merged to master (it is an error prone process because of other patches I maintain) so a next tag could be really useful for me and I guess for many others as well, plus it's good for testing and feedback.

[asturur]

that would be nice! i think is useful for many people.

[ShaMan123]

OK, how do we make this happen?
Git actions is a stranger to me.

[ShaMan123]

Docs:
https://github.com/actions/starter-workflows/tree/main/automation
https://docs.github.com/en/actions/creating-actions/about-actions

[asturur]

i think we can reuse our publish script and add an event for a commit on master

[asturur]

So we can duplicate this file, and call it npmpublish-next
https://github.com/fabricjs/fabric.js/blob/master/.github/workflows/npmpublish.yml

inside we change the on: condition with this one:

on:
  push:
    branches: [ master ]

we duplicate this file here
https://github.com/fabricjs/fabric.js/blob/master/publish.js

and we create one that is called publishnext.

Then we try it.

[ShaMan123]

Do you want to use the beta tag?
It has logic defined already. Or extends logic to accept any tag?
https://github.com/fabricjs/fabric.js/blob/master/publish.js#L13

[ShaMan123]

I see I can simply pass more args to the script file

[ShaMan123]

#7268 opened

[ShaMan123]

What do you think about a PR first comment action that builds a codesandbox fabric react app with the template I built #7178 ?

[ShaMan123]

I think codesandbox has an action out of the box for PRs