The settings page always returns the "latest version tag" instead of current.

[mertssmnoglu]

Describe the bug
The settings page always returns the "latest version tag" instead of current version like v2.0.1 or v2.0.2. That means we are unable to detect exact version of the Client side application.

To Reproduce
Steps to reproduce the behavior:

1. Open the browser
2. Go to Checkmate Dashboard
3. Click on 'Settings'
4. Scroll down to 'About' section.
5. See the version, it's always latest.

Expected behavior
Strictly assigned, exact version of the checkmate.

Code

Checkmate/Client/src/Pages/Settings/index.jsx

Lines 49 to 63 in cb7c118

	const fetchLatestVersion = async () => {
	let version = "unknown";
	try {
	const response = await networkService.fetchGithubLatestRelease();
	if (!response.status === 200) {
	throw new Error("Failed to fetch latest version");
	}
	version = response.data.tag_name;
	} catch (error) {
	createToast({ body: error.message || "Error fetching latest version" }); // Set error message
	} finally {
	setVersion(version);
	}
	};
	fetchLatestVersion();

Screenshots
Looks like I don't have permission to add screenshots here. Or it's disabled.

Additional context
If the current version is old, it can notify the user via toast notification to upgrade it's instance.

[jasneetsingh6114]

Hey, can you assign this issue to me. To solve this, I plan to modify the code to fetch the correct client version and display it accurately. Additionally, I will implement logic to check for version mismatches and notify users when an upgrade is available. This will ensure that the correct version is shown and help improve the overall user experience.

[gorkem-bwl]

Sorry for the late response. Assigned.