Skip to content

Commit

Permalink
Merge pull request #247 from pantheon-systems/release_1.4.1
Browse files Browse the repository at this point in the history
Release 1.4.1
  • Loading branch information
jazzsequence authored Aug 8, 2023
2 parents 3c63bd0 + d0a595e commit 550d56b
Show file tree
Hide file tree
Showing 9 changed files with 470 additions and 411 deletions.
9 changes: 6 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,17 +25,20 @@ The `master` branch matches the latest stable release deployed to [wp.org](wp.or
* Commit these changes with the message `Release X.Y.Z`
* Push the release branch up.
1. Open a Pull Request to merge `release_X.Y.Z` into `master`. Your PR should consist of all commits to `develop` since the last release, and one commit to update the version number. The PR name should also be `Release X.Y.Z`.
1. After all tests pass and you have received approval from a [CODEOWNER](./CODEOWNERS), merge the PR into `master`. "Rebase and merge" is preferred in this case. _Never_ squash to `master`.
1. After all tests pass and you have received approval from a [CODEOWNER](./CODEOWNERS), merge the PR into `master`. "Merge" is preferred in this case, not rebase. _Never_ squash to `master`.
1. Pull `master` locally, create a new tag (based on version number from previous steps), and push up. The tag should _only_ be the version number. It _should not_ be prefixed `v` (i.e. `X.Y.Z`, not `vX.Y.X`).
1. Confirm that the necessary assets are present in the newly created tag, and test on a WP install if desired.
1. Create a [new release](https://github.com/pantheon-systems/pantheon-advanced-page-cache/releases/new) using the tag created in the previous steps, naming the release with the new version number, and targeting the tag created in the previous step. Paste the release changelog from the `Changelog` section of [the readme](readme.txt) into the body of the release, including the links to the closed issues if applicable.
1. Create a [new release](https://github.com/pantheon-systems/pantheon-advanced-page-cache/releases/new) using the tag created in the previous steps, naming the release with the new version number, and targeting the tag created in the previous step. Use the "Generate Release Notes" button.
* This can be done with `gh` with the following: `gh release create "X.Y.Z" -t "X.Y.Z" --generate-notes`
1. Wait for the [_Release pantheon-advanced-page-cache plugin to wp.org_ action](https://github.com/pantheon-systems/pantheon-advanced-page-cache/actions/workflows/wordpress-plugin-deploy.yml) to finish deploying to the WordPress.org plugin repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes.
1. Check WordPress.org: Ensure that the changes are live on [the plugin repository](https://wordpress.org/plugins/pantheon-advanced-page-cache/). This may take a few minutes.
1. Following the release, prepare the next dev version with the following steps:
* `git checkout master`
* `git pull origin master`
* `git checkout develop`
* `git rebase master`
* Update the version number in all locations, incrementing the version by one patch version, and add the `-dev` flag (e.g. after releasing `1.2.3`, the new verison will be `1.2.4-dev`)
* Add a new `** Latest **` heading to the changelog
* Add a new `** X.Y.X-dev **` heading to the changelog in readme.txt and README.md
* `git add -A .`
* `git commit -m "Prepare X.Y.X-dev"`
* `git push origin develop`
9 changes: 6 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Pantheon Advanced Page Cache #

**Contributors:** [getpantheon](https://profiles.wordpress.org/getpantheon), [danielbachhuber](https://profiles.wordpress.org/danielbachhuber), [kporras07](https://profiles.wordpress.org/kporras07), [jspellman](https://profiles.wordpress.org/jspellman/), [jazzs3quence](https://profiles.wordpress.org/jazzs3quence/), [ryanshoover](https://profiles.wordpress.org/ryanshoover/), [rwagner00](https://profiles.wordpress.org/rwagner00/)
**Contributors:** [getpantheon](https://profiles.wordpress.org/getpantheon), [danielbachhuber](https://profiles.wordpress.org/danielbachhuber), [kporras07](https://profiles.wordpress.org/kporras07), [jspellman](https://profiles.wordpress.org/jspellman/), [jazzs3quence](https://profiles.wordpress.org/jazzs3quence/), [ryanshoover](https://profiles.wordpress.org/ryanshoover/), [rwagner00](https://profiles.wordpress.org/rwagner00/), [pwtyler](https://profiles.wordpress.org/pwtyler)
**Tags:** pantheon, cdn, cache
**Requires at least:** 4.7
**Tested up to:** 6.2
**Stable tag:** 1.4.0
**Tested up to:** 6.3
**Stable tag:** 1.4.1
**License:** GPLv2 or later
**License URI:** http://www.gnu.org/licenses/gpl-2.0.html

Expand Down Expand Up @@ -321,6 +321,9 @@ See [CONTRIBUTING.md](https://github.com/pantheon-systems/pantheon-advanced-page

## Changelog ##

### 1.4.1 ###
* Send the REST API response header to the result and not the REST server [[#237](https://github.com/pantheon-systems/pantheon-advanced-page-cache/pull/237)]. Props [@srtfisher](https://github.com/srtfisher) & [@felixarntz](https://github.com/felixarntz).

### 1.4.0 ###
* Bumped Dependencies [[236](https://github.com/pantheon-systems/pantheon-advanced-page-cache/pull/236)]
* Add filter `pantheon_should_add_terms` to allow disabling surrogate keys for posts' taxonomy terms [[239](https://github.com/pantheon-systems/pantheon-advanced-page-cache/pull/239)]
Expand Down
17 changes: 6 additions & 11 deletions composer.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions inc/class-emitter.php
Original file line number Diff line number Diff line change
Expand Up @@ -132,8 +132,8 @@ public static function filter_rest_pre_dispatch( $result, $server, $request ) {
*/
public static function filter_rest_post_dispatch( $result, $server ) {
$keys = self::get_rest_api_surrogate_keys();
if ( ! empty( $keys ) ) {
$server->send_header( self::HEADER_KEY, implode( ' ', $keys ) );
if ( ! empty( $keys ) && $result instanceof \WP_REST_Response ) {
$result->header( self::HEADER_KEY, implode( ' ', $keys ) );
}
return $result;
}
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "pantheon-advanced-page-cache",
"version": "1.4.0",
"version": "1.4.1",
"main": "Gruntfile.js",
"author": "Pantheon",
"devDependencies": {
Expand Down
4 changes: 2 additions & 2 deletions pantheon-advanced-page-cache.php
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
* Author URI: https://pantheon.io
* Text Domain: pantheon-advanced-page-cache
* Domain Path: /languages
* Version: 1.4.0
* Version: 1.4.1
*
* @package Pantheon_Advanced_Page_Cache
*/
Expand Down Expand Up @@ -79,7 +79,7 @@ function pantheon_wp_clear_edge_all() {

/**
* Prefix surrogate keys with the blog ID to provide compatibility with WPMS. See https://github.com/pantheon-systems/pantheon-advanced-page-cache/issues/196.
*
*
* @param array $keys Keys to be prefixed.
*/
function pantheon_wp_prefix_surrogate_keys_with_blog_id( $keys ) {
Expand Down
Loading

0 comments on commit 550d56b

Please sign in to comment.