From 452057c26861d215df6256376ff6a889bedaa5d0 Mon Sep 17 00:00:00 2001 From: Morten Piibeleht Date: Wed, 29 Nov 2023 12:45:13 +1300 Subject: [PATCH] Set version to 1.2.0 (#2362) --- CHANGELOG.md | 3 ++- Project.toml | 2 +- docs/src/checklists.md | 23 +++++++++-------------- 3 files changed, 12 insertions(+), 16 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index fd926af95e..5022ed4e95 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,7 +3,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). -## UNRELEASED +## Version [v1.2.0] - 2023-11-29 ### Changed @@ -1289,6 +1289,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 [v1.1.0]: https://github.com/JuliaDocs/Documenter.jl/releases/tag/v1.1.0 [v1.1.1]: https://github.com/JuliaDocs/Documenter.jl/releases/tag/v1.1.1 [v1.1.2]: https://github.com/JuliaDocs/Documenter.jl/releases/tag/v1.1.2 +[v1.2.0]: https://github.com/JuliaDocs/Documenter.jl/releases/tag/v1.2.0 [#198]: https://github.com/JuliaDocs/Documenter.jl/issues/198 [#245]: https://github.com/JuliaDocs/Documenter.jl/issues/245 [#487]: https://github.com/JuliaDocs/Documenter.jl/issues/487 diff --git a/Project.toml b/Project.toml index cf9fb128c4..3193c5cf67 100644 --- a/Project.toml +++ b/Project.toml @@ -1,6 +1,6 @@ name = "Documenter" uuid = "e30172f5-a6a5-5a46-863b-614d45cd2de4" -version = "1.1.2" +version = "1.2.0" [deps] ANSIColoredPrinters = "a4c015fc-c6ff-483c-b24f-f7ea428134e9" diff --git a/docs/src/checklists.md b/docs/src/checklists.md index 256b7ec403..9627ff7cd7 100644 --- a/docs/src/checklists.md +++ b/docs/src/checklists.md @@ -13,26 +13,21 @@ In preparation for a release, use the following checklist. These steps should be ## Pre-release - [ ] Change the version number in `Project.toml` - * If the release is breaking, increment MAJOR - * If the release adds a new user-visible feature, increment MINOR - * Otherwise (bug-fixes, documentation improvements), increment PATCH - - [ ] Update `CHANGELOG.md`, following the existing style (in particular, make - sure that the change log for this version has the correct version number - and date). - - [ ] Run `make changelog`, to make sure that all the issue references in - `CHANGELOG.md` are up to date. + * If the release is breaking, increment MAJOR + * If the release adds a new user-visible feature, increment MINOR + * Otherwise (bug-fixes, documentation improvements), increment PATCH + - [ ] Update `CHANGELOG.md`, following the existing style (in particular, make sure that the change log for this version has the correct version number and date). + - [ ] Run `make changelog`, to make sure that all the issue references in `CHANGELOG.md` are up to date. - [ ] Check that the commit messages in this PR do not contain `[ci skip]` ## The release - [ ] After merging the pull request, tag the release. There are two options for this: - 1. [Comment `[at]JuliaRegistrator register` on the GitHub commit.](https://github.com/JuliaRegistries/Registrator.jl#via-the-github-app) - 2. Use [JuliaHub's package registration feature](https://help.juliahub.com/juliahub/stable/contribute/#registrator) to trigger the registration. + 1. [Comment `[at]JuliaRegistrator register` on the GitHub commit.](https://github.com/JuliaRegistries/Registrator.jl#via-the-github-app) + 2. Use [JuliaHub's package registration feature](https://help.juliahub.com/juliahub/stable/contribute/#registrator) to trigger the registration. Either of those should automatically publish a new version to the Julia registry. - Once registered, the `TagBot.yml` workflow should create a tag, and rebuild the - documentation for this tag. These steps can take quite a bit of time (1 - hour or more), so don't be surprised if the new documentation takes a - while to appear. + - Once registered, the `TagBot.yml` workflow should create a tag, and rebuild the documentation for this tag. + - These steps can take quite a bit of time (1 hour or more), so don't be surprised if the new documentation takes a while to appear. ````