chore(release): 1.2.15

##### [Version 1.2.15](v1.2.14...v1.2.15) (2024-11-29) - Starter Sites Improvements
Codeinwp · Nov 29, 2024 · c2b3b3a · c2b3b3a
1 parent 4c6dbc2
commit c2b3b3a
Show file tree

Hide file tree

Showing 7 changed files with 13 additions and 15 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,7 @@
+##### [Version 1.2.15](https://github.com/Codeinwp/templates-patterns-collection/compare/v1.2.14...v1.2.15) (2024-11-29)
+
+- Starter Sites Improvements
+
 ##### [Version 1.2.14](https://github.com/Codeinwp/templates-patterns-collection/compare/v1.2.13...v1.2.14) (2024-11-28)
 
 - remove legacy Page Templates functionality

diff --git a/README.md b/README.md
@@ -39,12 +39,9 @@ Yes, you can. You can either chose to import one template or the entire starter
 
 ## Changelog ##
 
-##### [Version 1.2.14](https://github.com/Codeinwp/templates-patterns-collection/compare/v1.2.13...v1.2.14) (2024-11-28)
+##### [Version 1.2.15](https://github.com/Codeinwp/templates-patterns-collection/compare/v1.2.14...v1.2.15) (2024-11-29)
 
-- remove legacy Page Templates functionality
-- remove Template Cloud functionality for new users & users who weren't using the feature
-- we have launched a dedicated Templates Cloud plugin that offers advanced permission controls and additional features. which you can try from your Themeisle account
-- if you already have templates saved in the cloud, you can still use them in this plugin if you already have a license key set up
+- Starter Sites Improvements
 
 
 

diff --git a/composer.json b/composer.json
@@ -1,7 +1,7 @@
 {
   "name": "codeinwp/templates-patterns-collection",
   "description": "Templates and Patterns Collection Plugin",
-  "version": "1.2.14",
+  "version": "1.2.15",
   "license": "GPL-3.0-or-later",
   "homepage": "https://github.com/Codeinwp/templates-patterns-collection",
   "authors": [

diff --git a/includes/Main.php b/includes/Main.php
@@ -18,7 +18,7 @@ class Main {
 	 *
 	 * @var string Version string.
 	 */
-	const VERSION = '1.2.14';
+	const VERSION = '1.2.15';
 	/**
 	 * Sites Library API URL.
 	 *

diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "templates-patterns-collection",
-  "version": "1.2.14",
+  "version": "1.2.15",
   "description": "ThemeIsle Templates and Patterns Collection",
   "repository": {
     "type": "git",

diff --git a/readme.txt b/readme.txt
@@ -39,12 +39,9 @@ Yes, you can. You can either chose to import one template or the entire starter
 
 == Changelog ==
 
-##### [Version 1.2.14](https://github.com/Codeinwp/templates-patterns-collection/compare/v1.2.13...v1.2.14) (2024-11-28)
+##### [Version 1.2.15](https://github.com/Codeinwp/templates-patterns-collection/compare/v1.2.14...v1.2.15) (2024-11-29)
 
-- remove legacy Page Templates functionality
-- remove Template Cloud functionality for new users & users who weren't using the feature
-- we have launched a dedicated Templates Cloud plugin that offers advanced permission controls and additional features. which you can try from your Themeisle account
-- if you already have templates saved in the cloud, you can still use them in this plugin if you already have a license key set up
+- Starter Sites Improvements
 
 
 

diff --git a/templates-patterns-collection.php b/templates-patterns-collection.php
@@ -2,7 +2,7 @@
 /**
  * Plugin Name:       Starter Sites & Templates by Neve
  * Description:       This plugin gives you access to 100+ templates and ready-to-use starter sites. Neve theme is used for all the designs.
- * Version:           1.2.14
+ * Version:           1.2.15
  * Author:            Themeisle
  * Author URI:        https://themeisle.com
  * License:           GPLv3
@@ -54,7 +54,7 @@ function ti_tpc_load_textdomain() {
 	load_plugin_textdomain( 'templates-patterns-collection', false, dirname( plugin_basename( __FILE__ ) ) . '/languages/' );
 }
 
-define( 'TIOB_VERSION', '1.2.14' );
+define( 'TIOB_VERSION', '1.2.15' );
 define( 'TIOB_URL', plugin_dir_url( __FILE__ ) );
 define( 'TIOB_PATH', dirname( __FILE__ ) . '/' );
 define( 'TIOB_BASENAME', plugin_basename( __FILE__ ) );