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

Feature gate awareness for registries/packaging tooling #74

Open
vados-cosmonic opened this issue Jul 25, 2024 · 0 comments
Open

Feature gate awareness for registries/packaging tooling #74

vados-cosmonic opened this issue Jul 25, 2024 · 0 comments

Comments

@vados-cosmonic
Copy link

During the packaging SIG meeting yesterday (and the JS meeting) the idea of registries/packaging tooling being feature gate aware came up.

While this can take on many meanings, the primary one was the (possible) need to be able to specify certain features for packages.

There's also a conversation going on right now related to how feature gates should be handled, and the idea of a "target version" might also be a relevant idea (i.e. a settable parameter when retrieving/doing things with packages).

I think the simple answer here (which might be good enough) is that this is just a version resolution problem (this is somewhat different if the "target version" idea comes to fruition), and all items under all features should be returned regardless.

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

1 participant