Make [email protected] the default stable

Add versions in README.md
[skip actions]

Aliases/clickhouse

@@ -1 +1 @@
-../Formula/clickhouse@22.3.rb
+../Formula/clickhouse@22.6.rb

Aliases/clickhouse-client

@@ -1 +1 @@
-../Formula/clickhouse@22.3.rb
+../Formula/clickhouse@22.6.rb

Aliases/clickhouse-server

@@ -1 +1 @@
-../Formula/clickhouse@22.3.rb
+../Formula/clickhouse@22.6.rb

Aliases/clickhouse@stable

@@ -1 +1 @@
-../Formula/clickhouse@22.3.rb
+../Formula/clickhouse@22.6.rb

Formula/clickhouse@22.3.rb

@@ -19,6 +19,8 @@ class ClickhouseAT223 < Formula
     sha256                               monterey:       "c8064c8d6b69bc82f1cfd4d90e5c858b1eba1f93c7fe5e1ab1b91675e19c2e08"
   end
 
+  keg_only :versioned_formula
+
   depends_on "cmake" => :build
   depends_on "gawk" => :build
   depends_on "gettext" => :build

Formula/clickhouse@22.6.rb

@@ -19,8 +19,6 @@ class ClickhouseAT226 < Formula
     sha256                               monterey:       "188f8a604c4feecf123638337c92daf966f22862f0dfaedbfeeb469d9e4b167a"
   end
 
-  keg_only :versioned_formula
-
   depends_on "cmake" => :build
   depends_on "gawk" => :build
   depends_on "gettext" => :build

MAINTENANCE.md

@@ -79,7 +79,7 @@ Use the latest `Formula/[email protected]` formulae as a template:
     - adjust the configure/build flags and steps, if needed
   - make a PR from this branch into `main`, use `[email protected] XX.XX.XX.XX (new formula)` caption and an empty description (adjust the versions)
   - wait until all checks are green in the GitHub PR page, during which bottles will be created and uploaded as artifacts in GitHub
-  - once all checks are green, add `pr-pull` tag on the PR, this will trigger another action that will modify the formula, register the bottles in it, and will close (but not merge!) the PR; even though the PR will be shown as closed, the branch will be merged into `main` and the new versioned formula with bottles will be available to the users (they will need to do `brew update` to see the changes)
+  - once all checks are green, add `pr-pull` tag on the PR, this will trigger another action that will modify the formula, register the bottles in it, and will close (but **not** merge!) the PR; even though the PR will be shown as closed, the branch will be merged into `main` and the new versioned formula with bottles will be available to the users (they will need to do `brew update` to see the changes)
 - step 3: adjust the `README.md` and aliases
   - as a separate commit directly into `main` of the upstream:
     - add a `keg_only :versioned_formula` line to the previous latest versioned formula (the one you used as a template) right after the `bottle do ... end` section (compare with the older formulae for examples)
@@ -92,7 +92,9 @@ Use `brew livecheck ...` and `brew bump-formula-pr ...` to automatically detect
 
 - make sure you have an up-to-date Homebrew installation locally, and the tap is added to it
 - run `brew livecheck altinity/clickhouse/[email protected]` locally to see if a new version of the software is available (adjust version/formula name as needed), write down the new version, if any, as reported by `brew livecheck ...` - you will use it in the next steps
-- make sure you have a valid `GITHUB_TOKEN` in your `env` so that you will be able to push the changes made to the tap repo clone stored in your local brew's internal directories
+- make sure you have a valid `GITHUB_TOKEN` and `HOMEBREW_GITHUB_API_TOKEN` in your `env` so that you will be able to push the changes made to the tap repo clone stored in your local brew's internal directories
 - run `brew bump-formula-pr altinity/clickhouse/[email protected] --version=21.11.11.1 --no-fork`, it will create a PR with the new version (here `21.11.11.1`, as an example of a version that `brew livecheck ...` detected as one to upgrade to)
 - wait until all checks are green in the GitHub PR page, during which bottles will be created and uploaded as artifacts in GitHub
-- once all checks are green, add `pr-pull` tag on the PR, this will trigger another action that will modify the formula, register the bottles in it, and will close (but not merge!) the PR; even though the PR will be shown as closed, the branch will be merged into `main` and the new version of the formula with bottles will be available to the users (they will need to do `brew update` to see the changes)
+- once all checks are green, add `pr-pull` tag on the PR, this will trigger another action that will modify the formula, register the bottles in it, and will close (but **not** merge!) the PR; even though the PR will be shown as closed, the branch will be merged into `main` and the new version of the formula with bottles will be available to the users (they will need to do `brew update` to see the changes)
+- as a separate commit directly into `main` of the upstream:
+  - adjust the relevant version number in `README.md` to reflect the changes

README.md

@@ -7,20 +7,23 @@ clickhouse                       - alias, same as clickhouse@stable
 clickhouse-client                - alias, same as clickhouse@stable
 clickhouse-server                - alias, same as clickhouse@stable
 
-clickhouse@stable                - alias, always points to the latest stable versioned formula (clickhouse@22.3)
+clickhouse@stable                - alias, always points to the latest stable versioned formula (clickhouse@22.6)
 clickhouse@lts                   - alias, always points to the latest LTS versioned formula ([email protected])
 clickhouse@altinity-stable       - alias, always points to the latest Altinity-stable versioned formula ([email protected])
 
-[email protected]                  - the latest version
-[email protected]                  - keg-only
-[email protected]                  - keg-only
-[email protected]                 - keg-only
-[email protected]                 - keg-only
+[email protected]                  - the latest release, version: 22.6.3.35-stable
+[email protected]                  - keg-only, version: 22.5.2.53-stable
+[email protected]                  - keg-only, version: 22.4.6.53-stable
+[email protected]                  - keg-only, version: 22.3.8.39-lts
+[email protected]                  - keg-only, version: 22.2.3.5-stable
+[email protected]                  - keg-only, version: 22.1.4.30-stable
+[email protected]                 - keg-only, version: 21.12.4.1-stable
+[email protected]                 - keg-only, version: 21.11.11.1-stable
 
-[email protected]  - keg-only, the latest Altinity-stable version
+[email protected]  - keg-only, the latest Altinity-stable release, version: 21.8.15.15-altinitystable
 
-clickhouse-odbc                  - special variant
-clickhouse-cpp                   - special variant
+clickhouse-odbc                  - recommended variant, version: 1.1.10.20210822
+clickhouse-cpp                   - recommended variant, version: 2.1.0
 ```
 
 ## Quick start: one-liner
@@ -52,7 +55,7 @@ Note, that the installation doesn't require `sudo` and will deploy ClickHouse un
 
 ## Running ClickHouse server
 
-Do not use `sudo` ever. Do not start the ClickHouse server manually, instead use `brew services`:
+Do not use `sudo`, ever. Do not start the ClickHouse server manually, instead use `brew services`:
 
 ```sh
 brew services start clickhouse
@@ -112,7 +115,7 @@ Eventually, this list will be extended to also contain some of the previous vers
 
 Formulae will be built from sources automatically if the corresponding bottles are not available for your platform.
 
-If you want to see the progress, add `--verbose`:
+It could take several hours to build ClickHouse from sources, so you will probably want to monitor the progress. To enable verbose output for that scenario, add `--verbose` to `brew install ...`:
 
 ```sh
 brew install --verbose clickhouse