Publish release candidates when merging on reference branches. We need to pick a pre-release identifier (e.g. alpha, beta, pre, rc), so that a candidate would look something like: 3.0.0-pre.0 or 3.0.0-rc.1.
Motivation: Currently we are redeploying our npm packages with the same version (3.0.0-SNAPSHOT) which causes a bunch of integrity check failures and does not allow us to lock dependencies. Locking dependencies is key to have reproducible builds. By automating the release of elements whenever a merge happens, we can more easily lock dependency and avoid the integrity check errors.
- causes
-
NXP-29305 Force Web UI build to use packages.nuxeo.com
- Resolved
- depends on
-
NXBT-3339 Use DRY_RUN env var on Web UI staging namespace
- Resolved
- is related to
-
NXP-28504 Nightly release of nuxeo/nuxeo
- Resolved
-
NXBT-3340 Disable legacy CI jobs for Web UI and Elements for LTS 2021
- Open
-
NXBT-3341 Add cleanup policies for npm pre-release npm packages
- Resolved
-
NXP-29267 Align Web UI with Elements continuous releases
- Resolved
-
NXP-29268 Publish release candidates when merging on Web UI
- Resolved
- is required by
-
ELEMENTS-891 Review SNAPSHOT publishing of NPM packages
- Open
-
ELEMENTS-1196 Automate promotion of release candidates on Elements
- Resolved
- Is referenced in
- mentioned in
-
Page Loading...