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

Versioning system #60

Open
gsteinLTU opened this issue Mar 23, 2024 · 1 comment
Open

Versioning system #60

gsteinLTU opened this issue Mar 23, 2024 · 1 comment

Comments

@gsteinLTU
Copy link
Member

Ideally, old versions of extensions should be accessible in some way in order to preserve older demos. It makes sense to have a version number included with the extension metadata so we could support automatic upgrades with semantic versioning for projects made in older versions.

@dragazo has a good idea with using a Github Action. Maybe we can make it use a different branch for Pages, have the action check if the version number for one changed and then create a new folder for it (I'd keep the current URLs valid for the newest version). Maybe another generated file of available versions?

@gsteinLTU
Copy link
Member Author

A thought we had today, maybe it could upload the site to S3 instead of adding many copies of every asset for every extension to the repo.

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