Version out of date in bower.json about base64-js HOT 4 CLOSED

This is why bower.json was an unfortunate decision. No one remembers to keep it up to date. Will remove bower.json and see if that makes the warning go away.

from base64-js.

I installed this just now, and the bower.json file was downloaded with the repo, and is still incorrect in regards to version number.

from base64-js.

The version field should be removed from bower.json. Its use is deprecated as bower uses git tags, not bower.json.version.

If you use mversion patch -m, mversion minor -m, and mversion major -m before publishing to npm, then you will always have your git tags in sync with your npm version -- and this is just a good idea anyway.

from base64-js.

Or I'm completely wrong... because the git tags appear to be up to sync.

But I remember several versions ago getting deprecation notices about not using bower.json.version... weird...

from base64-js.