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
Right now, NPM packages are created and uploaded locally. This should be done by an automated pipeline.
Describe the solution you'd like
Ideally whenever the package version changes we have an automated pipeline which pushes a new package to the MRTK NPM feed so developers can download the updated package via the MRTK Feature Tool or Unity package manager.
Describe alternatives you've considered
Continue to do this by hand.
Additional context
See David Kline & Kurtis Eveleigh for more details.
The text was updated successfully, but these errors were encountered:
Describe the problem
Right now, NPM packages are created and uploaded locally. This should be done by an automated pipeline.
Describe the solution you'd like
Ideally whenever the package version changes we have an automated pipeline which pushes a new package to the MRTK NPM feed so developers can download the updated package via the MRTK Feature Tool or Unity package manager.
Describe alternatives you've considered
Continue to do this by hand.
Additional context
See David Kline & Kurtis Eveleigh for more details.
The text was updated successfully, but these errors were encountered: