From 179d6902132f1708ae43c379e58015d97fe50fe7 Mon Sep 17 00:00:00 2001
From: Zach Daniel <zach@zachdaniel.dev>
Date: Thu, 8 Jun 2023 23:43:32 -0400
Subject: [PATCH] chore: release version v2.6.0

---
 CHANGELOG.md | 13 +++++++++++++
 README.md    |  4 ++--
 mix.exs      |  2 +-
 3 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a249254..7a77667 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,19 @@ See [Conventional Commits](Https://conventionalcommits.org) for commit guideline
 
 <!-- changelog -->
 
+## [v2.6.0](https://github.com/zachdaniel/git_ops/compare/v2.5.6...v2.6.0) (2023-06-09)
+
+
+
+
+### Features:
+
+* AllowedTags: Adds allowed_tags option (#59)
+
+* AllowedTags: Add config allow_untagged? to tags
+
+* enable custom replace/pattern for readme versioning (#56)
+
 ## [v2.5.6](https://github.com/zachdaniel/git_ops/compare/v2.5.5...v2.5.6) (2023-03-07)
 
 
diff --git a/README.md b/README.md
index b35af4e..899ecfc 100644
--- a/README.md
+++ b/README.md
@@ -41,7 +41,7 @@ yourself using multiple scopes your commit is probably too big.
 ```elixir
 def deps do
   [
-    {:git_ops, "~> 2.5.6", only: [:dev]}
+    {:git_ops, "~> 2.6.0", only: [:dev]}
   ]
 end
 ```
@@ -108,7 +108,7 @@ version. Look at [this project's mix.exs](mix.exs) for an example.
 Most project readmes have a line like this that would ideally remain up to date:
 
 ```elixir
-    {:git_ops, "~> 2.5.6", only: [:dev]}
+    {:git_ops, "~> 2.6.0", only: [:dev]}
 ```
 
 You can keep that number up to date via `manage_readme_version`, which accepts
diff --git a/mix.exs b/mix.exs
index adeea08..f574bf8 100644
--- a/mix.exs
+++ b/mix.exs
@@ -2,7 +2,7 @@ defmodule GitOps.MixProject do
   use Mix.Project
 
   @source_url "https://github.com/zachdaniel/git_ops"
-  @version "2.5.6"
+  @version "2.6.0"
 
   def project do
     [