Skip to content

version number in bower.json seemingly not being honoured #1303

@lorenzo-stoakes

Description

@lorenzo-stoakes

Hi all,

This may be more my misunderstanding the rules on versioning, but I wonder whether there is an issue here - I tried to install the pubnub package only to find it defaults to version * when I bower install --save it, andbower info pubnub version doesn't return anything.

The project in question doesn't use git tags, however it does provide a version number in its bower.json.

According to the bower.json spec - 'Version should only be required if you are not using git tags' - which to me implies you can still have a version number regardless whether you use git tabs. Is this not the case?

I raise the issue here (as well as with the pubnub guys :) as this behaviour is surprising to me and seems to be a potential bug, or me missing something on my part.

Thanks, Lorenzo :)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions