Skip to content

Commit 6500524

Browse files
committed
- update changelog, versions for release
1 parent 153761c commit 6500524

File tree

3 files changed

+26
-2
lines changed

3 files changed

+26
-2
lines changed

CHANGELOG.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,19 @@
11
# Changelog
22

3+
## 2.3.0
4+
5+
## Update Notice
6+
7+
This release refactored some internals regarding how Clone fields and Group fields behave. There was no intentional breaking changes to the Schema, but if you are using Clone and Group fields there is a chance that if you were benefiting from a "bug as a feature" there might be some changes that could impact your Schema and/or resolvers, we recommend testing this update on a staging site to ensure things are still working for you as expected. Should you run into any problems, please [open a new issue](https://github.com/wp-graphql/wpgraphql-acf/issues/new/choose) and provide as much detail as possible to help us reproduce the scenario. Thanks! 🙏
8+
9+
## New Features
10+
11+
- [#193](https://github.com/wp-graphql/wpgraphql-acf/pull/193): feat: improved handling of clone and group fields
12+
13+
## Chores / Bugfixes
14+
15+
- [#194](https://github.com/wp-graphql/wpgraphql-acf/pull/194): ci: test against WordPress 6.5
16+
317
## 2.2.0
418

519
## New Features

readme.txt

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,6 +104,10 @@ Learn more about how [Appsero collects and uses data](https://appsero.com/privac
104104

105105
== Upgrade Notice ==
106106

107+
= 2.3.0 =
108+
109+
This release refactored some internals regarding how Clone fields and Group fields behave. There was no intentional breaking changes to the Schema, but if you are using Clone and Group fields there is a chance that if you were benefiting from a "bug as a feature" there might be some changes that could impact your Schema and/or resolvers, we recommend testing this update on a staging site to ensure things are still working for you as expected. Should you run into any problems, please [open a new issue](https://github.com/wp-graphql/wpgraphql-acf/issues/new/choose) and provide as much detail as possible to help us reproduce the scenario. Thanks! 🙏
110+
107111
= 2.1.0 =
108112

109113
While fixing some [performance issues](https://github.com/wp-graphql/wpgraphql-acf/pull/152) we had to adjust the fallback logic for mapping ACF Field Groups to the Schema if they do not have "graphql_types" defined.
@@ -116,6 +120,12 @@ This release is a complete re-architecture of WPGraphQL for ACF, introducing bre
116120

117121
== Changelog ==
118122

123+
= 2.3.0 =
124+
125+
**New Features**
126+
127+
**Chores / Bugfixes**
128+
119129
= 2.2.0 =
120130

121131
**New Features**

wpgraphql-acf.php

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
* Description: WPGraphQL for ACF seamlessly integrates Advanced Custom Fields with WPGraphQL.
55
* Author: WPGraphQL, Jason Bahl
66
* Author URI: https://www.wpgraphql.com
7-
* Version: 2.2.0
7+
* Version: 2.3.0
88
* Text Domain: wpgraphql-acf
99
* Requires PHP: 7.3
1010
* Requires at least: 5.9
@@ -31,7 +31,7 @@
3131
}
3232

3333
if ( ! defined( 'WPGRAPHQL_FOR_ACF_VERSION' ) ) {
34-
define( 'WPGRAPHQL_FOR_ACF_VERSION', '2.2.0' );
34+
define( 'WPGRAPHQL_FOR_ACF_VERSION', '2.3.0' );
3535
}
3636

3737
if ( ! defined( 'WPGRAPHQL_FOR_ACF_VERSION_WPGRAPHQL_REQUIRED_MIN_VERSION' ) ) {

0 commit comments

Comments
 (0)