Version number (staging) doesn't increment reliably

Edit Subject

Hello Troy:

Thank you for your feedback and apologies for the frustration. You are indeed correct about the version incrementing only when extension.js or background.js is modified. There is an internal discussion as to the relevance of the version number and whether we should provide it. Can I get your opinion as to why the version number is important for you to know from with the extension?

Regarding the resources, since you are only updating resources and not the extension.js file, in order to push the changes automatically, you must also make a change in the extension.js.

"Regarding the resources, since you are only updating resources and not the extension.js file, in order to push the changes automatically, you must also make a change in the extension.js. "

Thanks for that warning, it's no biggie once you know.

For us, the extension places a floating toolbar on the page with popout panels, one of which is like an 'about' page where it's convenient to show the version number. Although not in general release yet, we anticipate this will be helpful when our support people are checking what version a customer is using.

If I had a vote, I'd vote for keeping the version number functionality as it is now, with a +1 if it also incremented if .js resources changed.

But I wouldn't lose sleep provided the version number is available somewhere.

I'd second that, and actually go further by incrementing the version number when any Resources content is changed, not just js.

I think that the version number should be visible in the IDE so that I can tell if it matches the version number that I am testing locally.