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
We should add a wbt that checks the workload downlevel runtime versions against the new installer and fails if they are lower than the properties in eng/Versions.props
The text was updated successfully, but these errors were encountered:
This will help but it will still be quite fragile because installer often doesn't update the downlevel versions until after we should have already changed ours. We'll also need to do the same in emsdk to make sure that VS insertions go smoothly and we don't have the installer flow setup there (although we could add it)
If you're going off of the implicit version, I'm not sure this will work. Typically in VS main we'll have a .net preview that has N-1 implicit versions but N workloads. This is because VS added a package verification check that flags our workloads in main being behind their release branches. This check doesn't flag our implicit version/runtime.
Yeah, we could do implicit+1 on preview branches😉. We need to know ahead of time the versions that will be inserted into VS for a given branch so I guess we need a mechanism that will allow that or we need to produce the downlevel manifests somewhere other than runtime.
We should add a wbt that checks the workload downlevel runtime versions against the new installer and fails if they are lower than the properties in eng/Versions.props
The text was updated successfully, but these errors were encountered: