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

feat: update public and internal server versions #1729

Merged
merged 1 commit into from
Oct 21, 2023

Conversation

dudantas
Copy link
Member

Description:

This adds descriptive comments to clarify the purpose and usage of the version constants STATUS_SERVER_VERSION and SERVER_RELEASE_VERSION.

The STATUS_SERVER_VERSION constant is intended for external displays, like server listings on otlist (otservlist.com), and only shows the major version. This helps to minimize frequent changes in otlist categories.

On the other hand, SERVER_RELEASE_VERSION is the full version of the Canary Server, intended for internal use. It helps in identifying the exact state of the server software.

Changes:

Added comments to STATUS_SERVER_VERSION explaining its usage for external displays, particularly on otlist.
Added comments to SERVER_RELEASE_VERSION explaining its purpose for internal use to identify the server's exact version.

@dudantas dudantas changed the title feat: change server version to new release and create internal version feat: update public and internal server versions Oct 21, 2023
@dudantas dudantas merged commit 1cdf8bb into main Oct 21, 2023
@dudantas dudantas deleted the feat-change-release-version branch October 21, 2023 05:43
@dudantas dudantas restored the feat-change-release-version branch October 21, 2023 05:43
@dudantas dudantas deleted the feat-change-release-version branch October 21, 2023 05:44
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants