clasp deploy does not publish a new version of a Google Docs add-on

I might be misunderstanding the term “deployment” in the context of this CLI. I expect that when I deploy a new version of my add-on, it would publish a new version of the add-on.

Expected Behavior

That clasp deploy {version} would publish a new version of my Google docs add-on.

Actual Behavior

After running the above command and test out the published add-on, I don’t see the changes in the version used above.

Steps to Reproduce the Problem

1. Publish an add-on with initial functionality
2. Make some noticeable changes to the add-on (so that you know if it gets published)
3. Use clasp push to get your changes into your Google script
4. Use clasp version and clasp deploy {version} to deploy your changes
5. Test out add-on to see the published changes

Specifications

• Node version (node -v): v8.9.4
• Version (npm list | grep clasp): 1.1.1
• OS (Mac/Linux/Windows): Windows

[grant]

I don’t plan to integrate the Chrome Webstore API in clasp anytime soon. That would be out of scope of this tool at the moment. There may be other CLIs that are dedicated for this case.

Thanks for the issue though. Feel free to still comment here if you think differently.

[grant]

@ryanolsonx The process of publishing an add-on is described here:

https://developers.google.com/apps-script/add-ons/publish

Interacting with the Chrome Web Store sounds like a good idea for a different CLI as it seems like a big set of commands with various options. It would be great if we could describe how to tie these two processes together.

Looks like there’s already progress with an API/CLI:

API: https://developer.chrome.com/webstore/using_webstore_api CLI: https://github.com/DrewML/chrome-webstore-upload-cli npm: https://www.npmjs.com/package/chrome-store-api

Please comment if you try that CLI out and find success.