Migrate to tags based releases

[gillibrand]

Add tags: true for Expand Selection to Function (JavaScript) package for future updates.

Just a switch to tags based versioning. The command, keys, etc. are unchanged since... a long time. Only a recent bug fix.

• I'm the package's author and/or maintainer.
• I have have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. ** (It DOES add, but is an old package that always did, so not a change.)
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.

My package is ...

There are no packages like it in Package Control.

My package is similar to ... However it should still be added because ...

[packagecontrol-bot]

Automated testing result: SUCCESS

Packages modified:
  - Expand Selection to Function (JavaScript)

[braver]

Please remember to stick to semver tags, so 1.1.0 instead of 1.1.