Skip to content

Commit

Permalink
Resolves inconsistency issues between WordPress (Composer Managed) de…
Browse files Browse the repository at this point in the history
…velopment repository and the upstream repository.

Additional minor updates and fixes included in this update. For more information see https://docs.pantheon.io/release-notes/2024/08/wordpress-composer-managed-1-32-0
  • Loading branch information
jazzsequence authored Aug 6, 2024
1 parent 35c3642 commit 06c308a
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,8 @@
### v1.32.0 (2024-08-15)
### v1.32.0 (2024-08-06)
* This update primarily fixes consistency issues between the development repository ([`pantheon-systems/wordpress-composer-managed`](https://github.com/pantheon-systems/wordpress-composer-managed)) and the upstream repository ([`pantheon-upstreams/wordpress-composer-managed`](https://github.com/pantheon-upstreams/wordpress-composer-managed)). Most notably, this update removes decoupled packages that were erroneously being added to the non-decoupled upstream (and are not included in this repository).
* Fixes issues with subdomain multisite testing ([#148](https://github.com/pantheon-systems/wordpress-composer-managed/pull/148))
* Updates automation steps to check PRs for "mixed" commits ([#146](https://github.com/pantheon-systems/wordpress-composer-managed/pull/146)) and adds handling for merge commits and conflicts ([#152](https://github.com/pantheon-systems/wordpress-composer-managed/pull/152))
* Moves cookie settings inside the pantheon environment check ([#151](https://github.com/pantheon-systems/wordpress-composer-managed/pull/151))

### v1.31.1 (2024-07-29)
* Removes code that for handling wp-admin URLs. ([#143](https://github.com/pantheon-systems/wordpress-composer-managed/pull/143)) This code was not working as intended and testing revealed it to be unnecessary.
Expand Down

0 comments on commit 06c308a

Please sign in to comment.