You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: