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
Once we cut a stable release we should ditch the nightly-<sha> versions and instead use something semver compatible, e.g. x.y.z-nightly.n+<sha>, where:
x.y.z is the next version to be released, or just the latest version with a minor patch (e.g. if latest is x.y.z, then we would use x.y.(z+1))
-nightly.n is the prerelease label (as per semver spec), which is used to order releases (which is why n would be the nightly number)
+<sha> is metadata that semver does not consider for version ordering
For example, this would be the order of a number of releases and their pre-releases (first one is latest)
Once we cut a stable release we should ditch the
nightly-<sha>
versions and instead use something semver compatible, e.g.x.y.z-nightly.n+<sha>
, where:x.y.z
is the next version to be released, or just the latest version with a minor patch (e.g. if latest isx.y.z
, then we would usex.y.(z+1)
)-nightly.n
is the prerelease label (as per semver spec), which is used to order releases (which is whyn
would be the nightly number)+<sha>
is metadata that semver does not consider for version orderingFor example, this would be the order of a number of releases and their pre-releases (first one is latest)
This is a breaking change so it should only be considered in the new
foundryup
. Additionally this requires changes to the release workflowThe text was updated successfully, but these errors were encountered: