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

Design high-level versioning for extensions #661

Open
tjcouch-sil opened this issue Dec 1, 2023 · 2 comments
Open

Design high-level versioning for extensions #661

tjcouch-sil opened this issue Dec 1, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@tjcouch-sil
Copy link
Member

tjcouch-sil commented Dec 1, 2023

User Story
As an extension developer, I want to be able to update my extension so that other extension developers get latest functionality.

Description
Design what extension versioning should look like. Should the version be put anywhere other than in the manifest? How does versioning interact with sharing types? Should the extension module contain the major version number? Should newer versions of extensions always be loaded regardless of priority in the extension order?

See this discussion for some context.

@irahopkinson
Copy link
Contributor

The usual place to put the version is in package.json so it should at least be there.

@Sebastian-ubs
Copy link
Contributor

I've added a new story for the question about compatibity / dependencies between extensions and the platform and among each other: #664

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 📥 For Consideration
Development

No branches or pull requests

3 participants