Tag and update tags on each release

[XhmikosR]

It's a common practice in actions to use the same tag for minor/patch versions so that the consumers of the action don't need to update manually.

I'm unsure how this is handled automatically, but there must be some way.

For example actions/setup-node@v2.

[jackyef]

I think that's definitely doable via some tagging, which seems to be what actions/checkout does. I would look into streamlining the release process as well while I am at it.

While we are on the subject, this action is still on version 0. I originally wrote this action for myself, but I am pleased to see more people find it useful! Do you think at it's current state, it is sufficient to be promoted to v1?

[XhmikosR]

I think you should switch to using the bundlewatch API first (#18), set up some linting and automatic deployments so that you remove lib/main.js from the repo and then make it v1.0 :)