feat: Alpha release workflows
Before continuing, I would like to get a release of the runtime as-is under an alpha tag to check that everything works.
After this, I still need to investigate how to allow the main vite plugin to consume the new runtime from the workspace for local development while consuming the npm package when published. That seems to be what pnpm deploy is for.
For now, publishing the actual plugin as alpha-2 has no actual changes yet, and probably unnecessary, but I do want to get the runtime published to npm. Once it's up, I will test it with the implementation property to make sure everything works.
Yeah I can bump permissions for you. Are you publishing a new package or anything?
Yeah I can bump permissions for you. Are you publishing a new package or anything?
@SunsetFi can you share your idea please? Thanks
Yes, we want to publish @module-federation/vite-runtime. Initially it won't have a 'latest' tag, and I would like to also publish a copy of @module-federation/vite with an alpha tag at a later date, once the former makes its way onto npm.
@gioboa Any movement on this? Can we get the new NPM package?
@gioboa Any movement on this? Can we get the new NPM package?
I really would like to going on with this but I don't have permissions on this organisation for that