search

bower / registry

The Bower registry
https://registry.bower.io/packages
MIT License
292 stars 66 forks source link

Changed github endpoint for the svg.js package #287

Closed Fuzzyma closed 4 years ago

Fuzzyma commented 5 years ago

We moved our bower-ready files to svg.js-bower and will start taging them there from 3.0 upwards.

Can you change the registry in a way, that users of old versions still get the right tag? And users requesting svg.js v3 and above will use the new repo?

Old New
https://github.com/svgdotjs/svg.js.git https://github.com/svgdotjs/svg.js-bower.git
sheerun commented 5 years ago

It's not possible, you can only point to one repository

Fuzzyma commented 5 years ago

well in that case, let the endpoint as it is for now. I might just register a new package for version 3 and above

sheerun commented 5 years ago

Major bump in semver should be enough

On Sat, Dec 1, 2018 at 4:06 PM Ulrich-Matthias Schäfer < notifications@github.com> wrote:

well in that case, let the endpoint as it is for now. I might just register a new package for version 3 and above

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bower/registry/issues/287#issuecomment-443432659, or mute the thread https://github.com/notifications/unsubscribe-auth/AAR2Dbu9rVPHXnQDFNK8mmHa0nlDNuR-ks5u0prugaJpZM4Y83rd .

Fuzzyma commented 5 years ago

@sheerun but when the github endpoint changes, every version below 3.0 is not accessible via bower anymore. Or are these versions cached on your servers?

sheerun commented 5 years ago

We don't cache anything. Just don't create separate repository, but bump semver on old one. Or move old repository to new location as well as all tags. Bower only cares about repository url and its git tags.

sheerun commented 5 years ago

I'd suggest you remove https://github.com/svgdotjs/svg.js-bower.git and leave bower pointing to your current repository. You don't need to support bower for 3.0.0 version as bower is deprecated. Everyone sane used version constraint like "svg.js": "^2.1.2" which means it'll still work for them, they just won't be able to update to svg 3.0.0

sheerun commented 4 years ago

If you still want to unregister / modify this package you can send PR against this repository that modifies db/packages.json file. Please include proof that you are owner of this package. Please also mind that even if we remove/modify entry in bower registry, bower clients can have cache saved which needs to be cleaned with bower cache clean for each user.