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
Copy file name to clipboardExpand all lines: docs/src/maintain/manage-releases.md
+41Lines changed: 41 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,47 @@ In rare cases, a second patch release might be necessary if the release is known
49
49
50
50
After the patch release has been published (or no patch release is necessary), close the release issue and inform the team that they can start merging in semver-minor changes again.
51
51
52
+
### Release Parameters
53
+
54
+
The following tables show examples of the option to select as `RELEASE_TYPE` when starting `eslint-js Release` (the `@eslint/js` package release) and `eslint Release` (the `eslint` package release) jobs on Jenkins to release a new version with the latest features. In both jobs, `main` should be selected as `RELEASE_BRANCH`.
55
+
56
+
|**HEAD Version**|**Desired Next Version**|**`eslint-js Release`<br>`RELEASE_TYPE`**|
57
+
| :---: | :---: | :---: |
58
+
|`9.25.0`|`9.25.1`|`patch`|
59
+
|`9.25.0`|`9.26.0`|`minor`|
60
+
|`9.25.0`|`10.0.0-alpha.0`|`alpha.0`|
61
+
|`10.0.0-alpha.0`|`10.0.0-alpha.1`|`alpha`|
62
+
|`10.0.0-alpha.1`|`10.0.0-beta.0`|`beta`|
63
+
|`10.0.0-beta.0`|`10.0.0-beta.1`|`beta`|
64
+
|`10.0.0-beta.1`|`10.0.0-rc.0`|`rc`|
65
+
|`10.0.0-rc.0`|`10.0.0-rc.1`|`rc`|
66
+
|`10.0.0-rc.1`|`10.0.0`|`major`|
67
+
68
+
|**HEAD Version**|**Desired Next Version**|**`eslint Release`<br>`RELEASE_TYPE`**|
69
+
| :---: | :---: | :---: |
70
+
|`9.25.0`|`9.25.1` or `9.26.0`|`latest`|
71
+
|`9.25.0`|`10.0.0-alpha.0`|`alpha`|
72
+
|`10.0.0-alpha.0`|`10.0.0-alpha.1`|`alpha`|
73
+
|`10.0.0-alpha.1`|`10.0.0-beta.0`|`beta`|
74
+
|`10.0.0-beta.0`|`10.0.0-beta.1`|`beta`|
75
+
|`10.0.0-beta.1`|`10.0.0-rc.0`|`rc`|
76
+
|`10.0.0-rc.0`|`10.0.0-rc.1`|`rc`|
77
+
|`10.0.0-rc.1`|`10.0.0`|`latest`|
78
+
79
+
When releasing a new version of the previous major line, the option to select as `RELEASE_TYPE` depends on whether the HEAD version is a prerelease or not. In both jobs, the corresponding development branch (for example, `v9.x-dev`) should be selected as `RELEASE_BRANCH`.
80
+
81
+
|**HEAD Version**|**Previous Major Line Version**|**Desired Next Version**|**`eslint-js Release`<br>`RELEASE_TYPE`**|
82
+
| :---: | :---: | :---: | :---: |
83
+
|`10.0.0-alpha.0`|`9.25.0`|`9.25.1`|`patch`|
84
+
|`10.0.0-alpha.0`|`9.25.0`|`9.26.0`|`minor`|
85
+
|`10.0.0`|`9.25.0`|`9.25.1`|`maintenance.patch`|
86
+
|`10.0.0`|`9.25.0`|`9.26.0`|`maintenance.minor`|
87
+
88
+
|**HEAD Version**|**Previous Major Line Version**|**Desired Next Version**|**`eslint Release`<br>`RELEASE_TYPE`**|
89
+
| :---: | :---: | :---: | :---: |
90
+
|`10.0.0-alpha.0`|`9.25.0`|`9.25.1` or `9.26.0`|`latest`|
91
+
|`10.0.0`|`9.25.0`|`9.25.1` or `9.26.0`|`maintenance`|
92
+
52
93
## Emergency Releases
53
94
54
95
An emergency release is unplanned and isn't the regularly scheduled release or the anticipated patch release.
0 commit comments