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

🔋 auto-update addon inside the editor #126

Closed
bitbrain opened this issue Sep 15, 2023 · 4 comments · Fixed by #134
Closed

🔋 auto-update addon inside the editor #126

bitbrain opened this issue Sep 15, 2023 · 4 comments · Fixed by #134
Labels
📦 feature A new piece of functionality 🎓 good first issue Good for newcomers
Milestone

Comments

@bitbrain
Copy link
Owner

Similar to other addons such as Godot Dialogue Manager we could introduce a button (where the version label is) to upgrade the addon.

@bitbrain bitbrain added 📦 feature A new piece of functionality 🎓 good first issue Good for newcomers labels Sep 15, 2023
@bitbrain bitbrain added this to the 1.0.0 milestone Sep 16, 2023
@bitbrain
Copy link
Owner Author

Ensure to also update the docs, this then should close #113

@Nemesis-AS
Copy link
Contributor

I'd like to work on this issue. But I have a question, let's say that there are multiple releases available to update, should the user be allowed to choose which version they'd like to update?

@Nemesis-AS
Copy link
Contributor

Also, if there is an update with breaking changes, I'd suggest adding some sort of header in the release notes which can be read by the updater and displayed to the user within Godot so they don't end up breaking their project by updating.

An example of the breaking changes header would be
:#: Breaking Change 1
:#: Breaking Change 2
Then the updater can look for :#: and display those lines to the user

@bitbrain
Copy link
Owner Author

let's say that there are multiple releases available to update

In case a user "skips" a release, we should always offer them the latest version.

Also, if there is an update with breaking changes

rendering the markdown from the release notes should be sufficient. In case of breaking changes, I will mention it in the Github release description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 feature A new piece of functionality 🎓 good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants