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

Allow minor/patch versions for Zowe/imperative packages #1968

Closed
roman-kupriyanov opened this issue Nov 16, 2023 · 3 comments
Closed

Allow minor/patch versions for Zowe/imperative packages #1968

roman-kupriyanov opened this issue Nov 16, 2023 · 3 comments
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits v3 prospective changes for v3

Comments

@roman-kupriyanov
Copy link

Is your feature or enhancement request related to a problem or limitation? Please describe

Zowe/imperative package depends on numerous packages and all of them specified with a strict version selector (e.g. [email protected]). Since they are updating not frequently, it is always a chance to stuck with unsupported/deprecated versions of the transitive dependencies. Relaxing the rules may help extenders to update the transitive dependencies on their side, to possibly be up to date with some latest bug and vulnerability fixes.

Describe your enhancement idea

Allow the minor/patch versions of the dependencies to be specified in Zowe/imperative's package.json with ^ or at least ~ selectors (e.g. yargs@^15.3.1 or yargs@~15.3.1).

Describe alternatives you've considered

Alternatively, we are using a resolution mechanism with yarn, but sometimes it is impossible to resolve the dependencies correctly.

Provide any additional context

None.

@roman-kupriyanov roman-kupriyanov added enhancement New feature or request new The issue wasn't triaged yet labels Nov 16, 2023
Copy link

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@JTonda JTonda added priority-medium Not functioning - next quarter if capacity permits v3 prospective changes for v3 and removed new The issue wasn't triaged yet labels Nov 20, 2023
@JTonda
Copy link

JTonda commented Nov 20, 2023

Potential conformance criteria for v3 so that plug-ins are kept safe after versions constraints are loosened.

@adam-wolfe
Copy link
Contributor

Resolved by #1975. To be available in V3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits v3 prospective changes for v3
Projects
Status: Closed
Development

No branches or pull requests

3 participants