Skip to content

Commit

Permalink
Merge pull request #6284 from kit-ty-kate/post-2.3.0-rc1
Browse files Browse the repository at this point in the history
Port missing changelog from the 2.3 branch and improve release steps
  • Loading branch information
rjbou authored Nov 12, 2024
2 parents 8ac9c1b + 2e924e6 commit 6542fc6
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 1 deletion.
15 changes: 15 additions & 0 deletions CHANGES
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,21 @@ repositories (changes that are automatically handled by the format upgrade tools
are not marked). Those prefixed with "(+)" are new command/option (since
2.1.0~alpha2).

2.3.0~rc1:
* Improve the release script by adding a NetBSD/x86_64 binary
[#6258 @kit-ty-kate]

2.3.0~beta2:
* Fix the detection of the current terminal size
[#6244 @kit-ty-kate - fix #6243]
* Improve the release script by upgrading the platform building the Linux
binaries to Alpine 3.20, the FreeBSD binary to FreeBSD 14.1 and the
OpenBSD binary to OpenBSD 7.6 [#6237 @kit-ty-kate]
* Make the release script produce a Linux/riscv64 binary [#6237 @kit-ty-kate]
* API changes
* `OpamStubs.get_stdout_ws_col`: new Unix-only function returning the
number of columns of the current terminal window [#6244 @kit-ty-kate]

2.3.0~beta1:
* Fix an opam 2.1 regression where the initial pin of a local VCS directory
would store untracked and ignored files. Those files would usually be
Expand Down
2 changes: 1 addition & 1 deletion release/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
* update version in all the opam files and in configure.ac
* run `make configure` to regenerate `./configure` [checked by github actions]
* update copyright headers
* if you're releasing the first final release of a new branch (e.g. 2.2.0): make sure `root_version` in OpamFile.ml is set to the final release number (e.g. for 2.2.0, root_version should be 2.2). Make sure that opamFormatUpgrade.ml also contains an upgrade function from the previous version (that function will most likely be empty)
* if you're releasing the first final release of a new branch (e.g. 2.2.0) and the `root_version` has changed since the previous stable version (e.g. 2.1.6): make sure `root_version` in OpamFile.ml is set to the final release number (e.g. for 2.2.0, `root_version` should be 2.2). Make sure that `opamFormatUpgrade.ml` also contains an upgrade function from the previous version (that function will most likely be empty), and that `opamroot-versions.test` is updated accordingly too.
* run `make tests`, `opam-rt` [checked by github actions]
* update the CHANGE file: take `master_changes.md` content to fill it

Expand Down

0 comments on commit 6542fc6

Please sign in to comment.