Prepare 0.50.0-SNAPSHOT, update releasing notes (#2102)

CHANGELOG.md

@@ -2,6 +2,16 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](https://semver.org/).
 
+## Unreleased
+
+### Added
+
+### Removed
+
+### Fixed
+
+### Changed
+
 ## [0.50.0] - 2023-06-29
 
 ### Deprecation of ktlint-enable and ktlint-disable directives

RELEASING.md

@@ -10,10 +10,11 @@ Note: These steps should be done directly in the pinterest/ktlint repository, no
 4. Add the new release to the bottom of the `CHANGELOG.md` file.
 5. Push your changes to the branch, and merge it to `master`.
 6. Update your local `pinterest/ktlint` `master` branch; verify you see the `gradle.properties` and `CHANGELOG.md` changes locally.
-7. Add a tag with the new release version, and push it directly to remote (e.g. `git tag 0.50.0 && git push origin 0.50.0`). This will kick off the [Release workflow](https://github.com/pinterest/ktlint/actions/workflows/release.yml).
+7. Add a tag with the new release version, and push it directly to remote (e.g. `git tag 0.50.0 && git push origin 0.50.0`). This will kick off the [Release workflow](https://github.com/pinterest/ktlint/actions/workflows/release.yml).Important: when you get an error like `HttpError: refusing to allow a Personal Access Token to create or update workflow '.github/workflows/automerge-triggers.yml' without 'workflow' scope`, the Github personal access token is most likely expired. When this happens on the bump of the Homebrew formula, the personal access token of @shashachu needs to be updated.
 8. Close and release the repo on Sonatype. (Only Pinterest employees can do this.)
-9. Find the `<release>-update-refs` branch in the repo (created by the `.announce` script) and merge it.
-10. Update `gradle.properties` with the new `SNAPSHOT` version, and add the section below to the top of `CHANGELOG.md` and commit. (This can be done directly in the main repo or in your fork.)
+9. The `.announce` script has created the `<release>-update-refs` branch in the repo. Create a new pull request (https://github.com/pinterest/ktlint/compare) and merge it to master.
+10. Merge of branch `<release>-update-refs` to master starts the `Publish release documentation` and `Publish snapshot documentation` workflows. Check that both workflows succeed (https://github.com/pinterest/ktlint/actions). Also check that the documentation has actually been published on https://pinterest.github.io/ktlint/latest.
+11. Update `gradle.properties` with the new `SNAPSHOT` version, and add the section below to the top of `CHANGELOG.md` and commit. (This can be done directly in the main repo or in your fork.)
 ```markdown
 ## Unreleased
 

gradle.properties

@@ -1,4 +1,4 @@
-VERSION_NAME=0.50.0
+VERSION_NAME=0.50.1-SNAPSHOT
 GROUP=com.pinterest.ktlint
 
 POM_DESCRIPTION=An anti-bikeshedding Kotlin linter with built-in formatter.