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

Any special reason why puppetlabs modules in metadata.json has upper limit of versions? #23

Open
dniel opened this issue Jan 26, 2018 · 4 comments

Comments

@dniel
Copy link

dniel commented Jan 26, 2018

Im trying to use this module with puppet5 and puppetlabs-registry has been updated to version 2.0.1 and better puppet5 support. But puppetlibrarian doesnt like the upper limit of 2.0 version in this module.

@jdavisp3
Copy link
Contributor

No special reason I know of. We need to support puppet 3 but patches that preserve backwards compatibility will be accepted, thanks!

@trekytech7
Copy link

I didn't want to make a duplicate issue :).

Please add support for REGISTRY 2.x:
At present puppetlabs-registry latest is 2.1.0 Please update to support newest version.
ie:
Warning: Module 'puppetlabs-registry' (v2.1.0) fails to meet some dependencies:
'counsyl-windows' (v1.0.6) requires 'puppetlabs-registry' (>= 1.1.0 <2.0.0)

Thx

@jdavisp3
Copy link
Contributor

jdavisp3 commented Mar 9, 2019

Feel free to make a pull request.

@ghost
Copy link

ghost commented Apr 20, 2020

had to remove this from my modules due to the upper limits even tho it works great with the latest versions

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

No branches or pull requests

3 participants