Add workflow to help automate version numbers during releases

[justlevine]

Description

It seems we've been forgetting to update the WPGRAPHQL_VERSION since we moved it to constants.php

wp-graphql/constants.php

Line 21 in 1051357

define( 'WPGRAPHQL_VERSION', '1.16.0' );

Steps to reproduce

add_action( 'plugins_loaded', static function() {
  if (  defined( 'WPGRAPHQL_VERSION' ) && version_compare( WPGRAPHQL_VERSION, '1.19.0, '<' ) ) {
    error_log( 'This should only get logged if the version is less than 1.19.0' );
  }
 } );

Additional context

Maybe we should create a release CI that automatically commits the version bump in all the places we need it (constants, headers, @since @todo, @deprecated @todo etc). Or just an official checklist.

WPGraphQL Version

1.19.0

WordPress Version

6.4.2

PHP Version

8.1.15

Additional environment details

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have disabled ALL plugins except for WPGraphQL.

• Yes
• My issue is with compatibility with a specific WordPress plugin, and I have listed all my installed plugins (and version info) above.

[jasonbahl]

@justlevine thanks for catching this. And yes, I think it makes sense to automate this more to prevent this in the future. Will work on a script to help with this.

Thanks! 🙌🏻

[josephfusco]

For reference, Faust.js handles this via a node script that runs before an automated release PR is created. https://github.com/wpengine/faustjs/blob/canary/scripts/versionPlugin.js