I was unnecessarily complicating the nightly releases. This PR simplifies the flow and eliminates the package versioning conflicts the workflow was running into previously.
Not having the --preid in the package.json command means that, if left unspecified when called manually, it will use the default of beta.
I've been able to create multiple releases using the workflow, e.g. for stream-model, even without any changes to the package.
I was able to update the e2e tests to use the new versions and they compiled. I'm also going to run them and see if they pass after auto-updating.
I was unnecessarily complicating the nightly releases. This PR simplifies the flow and eliminates the package versioning conflicts the workflow was running into previously.
Not having the
--preidin thepackage.jsoncommand means that, if left unspecified when called manually, it will use the default ofbeta.I've been able to create multiple releases using the workflow, e.g. for stream-model, even without any changes to the package.
I was able to update the e2e tests to use the new versions and they compiled. I'm also going to run them and see if they pass after auto-updating.