Updated project version after build [skip ci]

github-actions[bot] · github-actions[bot] · commit c6ca07100568 · 2026-04-22T08:12:28.000+01:00
diff --git a/BUILD_NO b/BUILD_NO
@@ -1 +1 @@
-4342
+4361
diff --git a/docs/about/authors.md b/docs/about/authors.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 ### utPLSQL v3 Major Contributors 
 
diff --git a/docs/about/license.md b/docs/about/license.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 # Version Information
 
diff --git a/docs/about/project-details.md b/docs/about/project-details.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 # utPLSQL Project Details
 
diff --git a/docs/about/support.md b/docs/about/support.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 # How to get support
 
diff --git a/docs/index.md b/docs/index.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 ## What is utPLSQL
 
diff --git a/docs/userguide/advanced_data_comparison.md b/docs/userguide/advanced_data_comparison.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 # Advanced data comparison
 
diff --git a/docs/userguide/annotations.md b/docs/userguide/annotations.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 Annotations are used to configure tests and suites in a declarative way similar to modern OOP languages. This way, test configuration is stored along with the test logic inside the test package.
 No additional configuration files or tables are needed for test cases. The annotation names are based on popular testing frameworks such as JUnit.
diff --git a/docs/userguide/best-practices.md b/docs/userguide/best-practices.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 The following are best practices we at utPLSQL have learned about PL/SQL and Unit Testing. 
 
diff --git a/docs/userguide/coverage.md b/docs/userguide/coverage.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 utPLSQL comes with a built-in coverage reporting engine. The code coverage reporting uses package DBMS_PROFILER (and DBMS_PLSQL_CODE_COVERAGE on Oracle database version 12.2 and above) provided with Oracle database.
 Code coverage is gathered for the following source types:
diff --git a/docs/userguide/exception-reporting.md b/docs/userguide/exception-reporting.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 utPLSQL is responsible for handling exceptions wherever they occur in the test run. The framework is trapping most of the exceptions so that the test execution is not affected by individual tests or test packages throwing an exception.
 The framework provides a full stacktrace for every exception that was thrown. The reported stacktrace does not include any utPLSQL library calls in it.
diff --git a/docs/userguide/expectations.md b/docs/userguide/expectations.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 ## Expectation concepts 
 
diff --git a/docs/userguide/getting-started.md b/docs/userguide/getting-started.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 # Getting started with TDD and utPLSQL
 
diff --git a/docs/userguide/install.md b/docs/userguide/install.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 ## Supported database versions
 
diff --git a/docs/userguide/querying_suites.md b/docs/userguide/querying_suites.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 ## Obtaining information about suites 
 
diff --git a/docs/userguide/reporters.md b/docs/userguide/reporters.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 utPLSQL provides several reporting formats. The sections below describe most of them. 
 
diff --git a/docs/userguide/running-unit-tests.md b/docs/userguide/running-unit-tests.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 utPLSQL framework provides two main entry points to run unit tests from within the database: 
 
diff --git a/docs/userguide/upgrade.md b/docs/userguide/upgrade.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)
 
 # Upgrading from version 2
 
diff --git a/sonar-project.properties b/sonar-project.properties
@@ -3,7 +3,7 @@ sonar.organization=utplsql
 sonar.projectKey=utPLSQL_utPLSQL
 # this is the name and version displayed in the SonarQube UI. Was mandatory prior to SonarQube 6.1.
 sonar.projectName=utPLSQL
-sonar.projectVersion=v3.1.14-develop
+sonar.projectVersion=v3.2.01-develop
 
 # Path is relative to the sonar-project.properties file. Replace "\" by "/" on Windows.
 # Since SonarQube 4.2, this property is optional if sonar.modules is set.
diff --git a/source/core/ut_utils.pks b/source/core/ut_utils.pks
@@ -21,7 +21,7 @@ create or replace package ut_utils authid definer is
    *
    */
 
-  gc_version                 constant varchar2(50) := 'v3.1.14.4342-develop';
+  gc_version                 constant varchar2(50) := 'v3.2.01.4361-develop';
     
   subtype t_executable_type      is varchar2(30);
   gc_before_all                  constant t_executable_type := 'beforeall';

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-![version](https://img.shields.io/badge/version-v3.1.14.4342--develop-blue.svg)`
	`1`	`+![version](https://img.shields.io/badge/version-v3.2.01.4361--develop-blue.svg)`
`2`	`2`
`3`	`3`	`### utPLSQL v3 Major Contributors`
`4`	`4`