Skip to content
This repository was archived by the owner on Jan 24, 2019. It is now read-only.
This repository was archived by the owner on Jan 24, 2019. It is now read-only.

Bower not updating to latest commit #131

@sartaj

Description

@sartaj

Currently, when using bower install angular-ui-utils, it installs the the original commit, not the latest commit, for 0.0.4. Here is the generated .bower.json from the folder:

{
  "author": "AngularUI Team",
  "name": "angular-ui-utils",
  "description": "AngularUI Utilities - Companion Suite for AngularJS",
  "version": "0.0.4",
  "homepage": "http://angular-ui.github.com",
  "main": "./modules/utils.js",
  "dependencies": {
    "angular": ">= 1.0.2"
  },
  "devDependencies": {
    "angular-mocks": "~1.0.5",
    "jquery": ">=1.6",
    "angular-ui-docs": "angular-ui/angular-ui-docs"
  },
  "_release": "0.0.4",
  "_resolution": {
    "type": "version",
    "tag": "v0.0.4",
    "commit": "fa7e14e6cb254b3166ff36060f30ed69b54e7152"
  },
  "_source": "git://github.com/angular-ui/ui-utils.git",
  "_target": "*",
  "_originalSource": "angular-ui-utils"
}

As you can see the commit installed is fa7e14e6cb254b3166ff36060f30ed69b54e7152, which is not the latest commit and doesn't have the latest bugfixes.

Is this intended behavior? If so, isn't that not good for critical bugfixes that need to be pushed to peoples bower components?

If it's unintended behavior, I presume it's because bower's version probably just looks for the first commit of a version it is looking for.

Perhaps the angular-ui-utils project should follow Semantic Versioning and append every bug fix with a number to avoid this issue?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions