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
In Scala.js, for cross-publishng to 0.6.x and 1.0.0-RC, it is common practice to use system env virable to switch Scala.js plugin version. One example can be found on circe.
For Scala.js cross-publishing, one will performe the steps like below:
Set system env to 0.6.31
Start sbt
Release to 0.6.31
Shutdown sbt
Start sbt
Set system env to 1.0.0-RC1
Release to 1.0.0-RC1
Shutdown sbt
Any idea to automate such process in single releaseProcess settings?
My understanding is that it is impossible because sbt can use/switch multiple version of scala-js sbt plugin in single instance.
The text was updated successfully, but these errors were encountered:
exoego
changed the title
How to automate multiple releases with different env variables
How to automate releasing for Scala.js 0.6 and 1.0
Jan 27, 2020
In Scala.js, for cross-publishng to
0.6.x
and1.0.0-RC
, it is common practice to use system env virable to switch Scala.js plugin version.One example can be found on circe.
For Scala.js cross-publishing, one will performe the steps like below:
0.6.31
0.6.31
1.0.0-RC1
1.0.0-RC1
Any idea to automate such process in single
releaseProcess
settings?My understanding is that it is impossible because sbt can use/switch multiple version of scala-js sbt plugin in single instance.
The text was updated successfully, but these errors were encountered: