Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update plugin version to 3.1.1 #7647

Merged
merged 1 commit into from
Jul 2, 2018
Merged

Update plugin version to 3.1.1 #7647

merged 1 commit into from
Jul 2, 2018

Conversation

nfmohit
Copy link
Member

@nfmohit nfmohit commented Jun 30, 2018

Description

This PR just updates the plugin version from 3.1.0 to 3.1.1

How has this been tested?

This has been tested by making sure that the plugin at Github repository is at the same version with the released version which is currently 3.1.1.

This was tested in WP 4.9.6, Gutenberg 3.1.1, Apache server with PHP 7.2.0 and MySQL 5.6.34. According to initial tests, the code doesn’t seem to affect any other areas.

Types of changes

This PR just changes the version number in the core plugin file and npm package files.

Checklist:

  • My code is tested.
  • My code follows the WordPress code style.
  • My code follows the accessibility standards.
  • My code has proper inline documentation.

@ajitbohra ajitbohra requested a review from mtias July 1, 2018 20:12
@gziolo gziolo requested a review from tofumatt July 2, 2018 04:46
@gziolo
Copy link
Member

gziolo commented Jul 2, 2018

@tofumatt, it looks like you didn’t merge back version bump.

Copy link
Member

@tofumatt tofumatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, well, true. I cherry-picked the version and from habits didn't think to put it in master because I released on a separate branch. But fair enough, I guess this should go in master.

@gziolo gziolo merged commit a2e29d2 into WordPress:master Jul 2, 2018
@aduth
Copy link
Member

aduth commented Jul 2, 2018

We should document a policy one way or the other here on patch releases. See also #4343.

@tofumatt
Copy link
Member

tofumatt commented Jul 2, 2018

I'll add it to #7607.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants