How to update your plugin/theme.

To release the new version, please do as follows:

Tag and push to GitHub, then upload the package by one of the ways as follows.

$ git tag 1.1.0
$ git push origin 1.1.0
  • 1.1.0 is a version number, it has to be the same as version number in your WordPress plugin.

  • You have to commit vendor the directory in your plugin.


A. Manually release the new version.

  1. Please visit "releases" in your GitHub repository.

  2. Choose a tag.

  3. Fill out the release note and title.

  4. Upload your plugin which is compressed with zip file. (Optional)

  5. Press "Publish release".


B. Automated release the new version with GitHub Actions.

You can upload the package automat GutHub Actions.

As for now, the GitHub Actions service is in beta, so you have to sign up for the Beta here

When the service is ready you will find the Actions tab on the top page of your repository, then follow the steps below:

  1. Then, copy the .github directory on the below url to the root directory of your local repository. getshifter/shifter-github-hosting-plugin-sample

  2. It must look like: /path_to_your_repository/.github/workflows/release.yml 

  3. Open the release.yml  file with your favourite editor and change some lines:

    1. You MUST change the PACKAGE_NAME to your package name.

      1. Also, if you need:

        1. change FILES_TO_ARCIVE

        2. comment out the composer install section

        3. uncomment npm install section

  4. After changing some lines, commit and push it to your GitHub repository.

Now when you push your tag to GitHub, the release package will be created automatically.

Example Projects

Please install an old version of the following projects, then you can see the update notice.

These projects deploy new releases automatically with GitHub Actions.
Please check .github/workflows/release.yml


C. Automated release the new version with Travis.

Also, you can use Automatic release with Travis.
Following is an example of an .travis.yml to make an automatic release.

You can generate deploy: section by The Travis Client like the following.

$ travis setup releases
Did this answer your question?