Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add entry to point to newer registry.bower.io package registry #100

Closed
wants to merge 1 commit into from

Conversation

jscharf
Copy link

@jscharf jscharf commented Jul 9, 2018

Overview

Does this PR close an existing issue?

Yes it closes issue #99.

Summary

Error when running bower install

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • I have evaluated if the README.md documentation needs to be updated
  • I have evaluated if the /tests/dummy/ app needs to be modified
  • I have evaluated if DocBlock headers needed to be added or updated
  • I have verified that lint and tests pass locally with my changes
  • If a fork of a dependent package had to be made to address the issue this PR closes:
    • I noted in the fork's README.md the reason the fork was created
    • I have opened an upstream issue detailing what was deficient about the dependency
    • I have opened an upstream PR addressing this deficiency
    • I have opened an issue in this repository to track this PR and schedule the removal of the usage of the fork

Semver

This project uses semver, please check the scope of this PR:

  • #none#
  • #patch#
  • #minor#
  • #major#

Examples:

  • NONE
    • README.md changes
    • test additions
    • changes to files that are not used by a consuming application (.travis.yml, .gitignore, etc)
  • PATCH
    • backwards-compatible bug fix
      • nothing about how to use the code has changed
      • nothing about the outcome of the code has changed (though it likely corrected it)
    • changes to demo app (/tests/dummy/)
  • MINOR
    • adding functionality in a backwards-compatible manner
      • nothing about how used to use the code has changed but using it in a new way will do new things
      • nothing about the outcome of the code has changed without having to first use it in a new way
      • addition of new CSS selectors
      • addition of new ember-hook selectors
  • MAJOR
    • incompatible API change
      • using the code how used to will cease working
      • using the code how used to will have a different outcome
      • any changes to CSS selector names
      • any removal of CSS selectors
      • any changes to ember-hook selectors
      • possibly changes to test helpers (depends on the changes made)
    • any changes to the dependencies entry in the package.json file

CHANGELOG

  • Add entry to point to newer registry.bower.io package registry

@jscharf jscharf requested a review from a team as a code owner July 9, 2018 19:04
@jscharf
Copy link
Author

jscharf commented Jul 17, 2018

I am closing this pull request because the issue is fixed in a later version of Bower (1.8.4) - see comment in #99 for more information.

@jscharf jscharf closed this Jul 17, 2018
@jscharf jscharf deleted the add-bower-registry branch July 17, 2018 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant