diff --git a/examples/deploy-on-publishing-a-new-release-and-attach-a-zip-file-to-the-release.yml b/examples/deploy-on-publishing-a-new-release-and-attach-a-zip-file-to-the-release.yml
index 90ce4a9..bfea5a0 100644
--- a/examples/deploy-on-publishing-a-new-release-and-attach-a-zip-file-to-the-release.yml
+++ b/examples/deploy-on-publishing-a-new-release-and-attach-a-zip-file-to-the-release.yml
@@ -80,21 +80,12 @@ jobs:
     # After the deploy, we also want to create a zip and upload it to the release on Github. We don't want
     # users to have to go to the repository to find our plugin :).
     - name: Upload release asset
-      uses: actions/upload-release-asset@v1
+      uses: softprops/action-gh-release@v2
       env:
         # Note, this is an exception to action secrets: GH_TOKEN is always available and provides access to
         # the current repository this action runs in.
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       with:
-        # Get the URL for uploading assets to the current release.
-        upload_url: ${{ github.event.release.upload_url }}
-
-        # Provide the path to the file generated in the previous step using the output.
-        asset_path: ${{ steps.deploy.outputs.zip-path }}
-
         # Provide what the file should be named when attached to the release (plugin-name.zip)
-        asset_name: ${{ github.event.repository.name }}.zip
-
-        # Provide the file type.
-        asset_content_type: application/zip
+        files: ${{ github.workspace }}/${{ github.event.repository.name }}.zip