feat(connections): warn then connecting to an end-of-life server COMPASS-9083

[kraenhansen]

Description

Merging this PR will:

• Add a warning modal similar to the "Non Genuine Connection Modal" shown when connecting to MongoDB 4.4.
  • With a link to https://www.mongodb.com/legal/support-policy/lifecycles
  • Only shown when the server is genuine.
  • Sends off a request to the update server, asking for the latest server version which is EOL.
• Remove the "cancel" button from the "Non Genuine Connection Modal", to align with the now modal and because it serves no purpose and is actually slightly misleading as connecting cannot be cancelled by pressing the button.
• Updates test fixtures to use server version 100.0.0, to avoid working around the new modal in existing tests.

Screen.Recording.2025-05-02.at.10.11.41.mov

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

• Will the build info be present and potentially misleading when connecting to a non-genuine server? And do we care about that?

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[kraenhansen]

😬 I just realized (and remembered) that @alenakhineika had already made a draft PR adding this #6805 🙈 I'll pick some of her ideas into this branch (as this has tests) and add a call to the update server.

[addaleax]

If we're already taking this from the buildInfo output, is there any reason not to use versionArray directly?

[kraenhansen]

Mostly that I wasn't aware that this was included in the build info.

Never the less, I expect these lines to go away and instead I'll be using "semver" like Alena did in her PR:

compass/packages/compass-connections/src/stores/connections-store-redux.ts

Lines 1459 to 1470 in f5fffe5

	export function isEndOfLifeServer(
	serverVersion: string | undefined | null
	): boolean {
	if (!serverVersion) {
	return true;
	}
	try {
	return semver.satisfies(serverVersion, `<=${getEoLServerVersion()}`);
	} catch (e) {
	return true;
	}
	}

[kraenhansen]

I wonder if there's a better place to put these. Some package intended to share constants across the main and renderer processes.

[kraenhansen]

I suggest hiding the cancel button on this as well, to keep things aligned and because canceling this modal won't stop connecting anyway.

[lerouxb]

This is a nit, but I'd personally probably have jumped through hoops to come up with two different names where one showEndOfLifeMongoDBWarningModal is the thunk action creator thingy and one is the function from the component. But I can live with this ;)

[kraenhansen]

TBH, I didn't pay too much attention to naming there as I was mostly copying from the code above:

compass/packages/compass-connections/src/stores/connections-store-redux.ts

Lines 2162 to 2171 in 32e0d30

	export const showNonGenuineMongoDBWarningModal = (
	connectionId: string
	): ConnectionsThunkAction<void> => {
	return (_dispatch, getState, { track }) => {
	const connectionInfo = getCurrentConnectionInfo(getState(), connectionId);
	track('Screen', { name: 'non_genuine_mongodb_modal' }, connectionInfo);
	void _showNonGenuineMongoDBWarningModal(connectionInfo);
	};
	};

[lerouxb]

I'm trying to understand under which circumstances this would be falsy?

[kraenhansen]

From the docs:

Only text which lacks digits will fail coercion (version one is not valid).

[lerouxb]

But.. will it throw or be falsy? You seem to be checking/accounting for both and it isn't clear to me that both can happen.

[kraenhansen]

The try-catch is mostly to be extra safe that these calls won't prevent the caller from progressing - if we're unsure, we'll opt on the safe side instead of propagating errors. This also handles if semverSatisfies or any future code added to the block throws for some reason.

The check for falsy coercedVersion is the known case of a malformed server version. This is mostly to handle that we might fail to determine a non-genuine server with a malformed version or a future MongoDB version which is not able to coerce, for some unknown reason.