From b1cb20cc2d5be0469dba5babfb2c57481deb4849 Mon Sep 17 00:00:00 2001
From: liquibot <64099989+liquibot@users.noreply.github.com>
Date: Thu, 1 Aug 2024 14:24:33 +0000
Subject: [PATCH] [maven-release-plugin] prepare for next development iteration

---
 pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pom.xml b/pom.xml
index dfbf66a..1e02183 100644
--- a/pom.xml
+++ b/pom.xml
@@ -10,7 +10,7 @@
 
     <groupId>org.liquibase.ext</groupId>
     <artifactId>liquibase-nochangeloglock</artifactId>
-    <version>4.29.1</version>
+    <version>4.30.0-SNAPSHOT</version>
 
     <name>Liquibase Extension Disable DatabaseChangeLogLock usage</name>
     <description>Disables locking logic Liquibase uses to ensure only one instance is running against a database at one
@@ -41,7 +41,7 @@
         <connection>scm:git:${project.scm.url}</connection>
         <developerConnection>scm:git:${project.scm.url}</developerConnection>
 		<url>https://github.com/liquibase/liquibase-nochangeloglock.git</url>
-		<tag>liquibase-nochangeloglock-4.29.1</tag>
+		<tag>HEAD</tag>
 	</scm>
 
 </project>