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

[Notes] Version notifications #10

Open
hickey opened this issue Oct 13, 2023 · 1 comment
Open

[Notes] Version notifications #10

hickey opened this issue Oct 13, 2023 · 1 comment
Milestone

Comments

@hickey
Copy link
Owner

hickey commented Oct 13, 2023

This is a planning issue. Looking from comments and suggestions from the community.

For a MeshChat instance to determine if a new version is available a well known URL needs to be queried for version information. The best source of information for this is the GitHub releases API. MeshChat needs to fail gracefully if the releases API can not be reached.

Releases should only be semver versions that are not labeled as pre-release or any other development state.

Alternatively, since MeshChat already know about one another in a zone, the version information can also be shared. While new releases will not be discovered until one instance is upgraded to the release, it does avoid dependency on external connections.

@hickey
Copy link
Owner Author

hickey commented Nov 4, 2023

Initial investigation in to the status.js file seems to indicate that adding the version to the API will not have any effect for backwards compatibility.

@hickey hickey added this to the 2.11 milestone Nov 18, 2023
@hickey hickey modified the milestones: v2.13.0, v2.14.0 Apr 6, 2024
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