From 4ae9d7934e9276d02b598a8887ccc1319f6f94fa Mon Sep 17 00:00:00 2001
From: Jeremy Goh <30731072+thatlittleboy@users.noreply.github.com>
Date: Sun, 18 Aug 2024 18:53:40 +0800
Subject: [PATCH] release: v1.9.0

---
 README.md              | 8 ++++----
 lgtm_db/__version__.py | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 5bc7893..737441c 100644
--- a/README.md
+++ b/README.md
@@ -90,14 +90,14 @@ Some personal notes on creating/editing gifs are in the [Github wiki](https://gi
 
 ### 📌 Release
 
-1. Create a new branch called `release-v1.9.0`, for example, from the `main` branch.
-1. Bump the version number in [`__version__.py`](lgtm_db/__version__.py) and commit with a commit message `release: v1.9.0`. And push up to remote.
+1. Create a new branch called `release-v1.10.0`, for example, from the `main` branch.
+1. Bump the version number in [`__version__.py`](lgtm_db/__version__.py) and commit with a commit message `release: v1.10.0`. And push up to remote.
 1. Create a PR, attach the following output
    ```shell
-   git log --oneline --no-decorate --perl-regexp --author='^(?!.*\[bot\]).*$' HEAD ^v1.8.0
+   git log --oneline --no-decorate --perl-regexp --author='^(?!.*\[bot\]).*$' HEAD ^v1.9.0
    ```
    to the PR description. Merge this branch into `main`.
-1. Then tag the ref, `git tag v1.9.0`, for example, on the `main` branch. Push the tags to remote.
+1. Then tag the ref, `git tag v1.10.0`, for example, on the `main` branch. Push the tags to remote.
 
 ## ⚡️ Inspiration
 
diff --git a/lgtm_db/__version__.py b/lgtm_db/__version__.py
index 29654ee..0a0a43a 100644
--- a/lgtm_db/__version__.py
+++ b/lgtm_db/__version__.py
@@ -1 +1 @@
-__version__ = "1.8.0"
+__version__ = "1.9.0"