chore: remove internal Node.js 18 build details

[MikeMcC399]

Situation

The following directories contain build files used to create Docker images for internal Cypress usage, based on the obsolete Node.js 18 version:

• base-internal/releases/node-18
• browsers-internal/releases/node-18

Node.js 18 entered end-of-life on Apr 30, 2025.

Cypress dropped support for Node.js 18 with the release of [email protected] on Aug 20, 2025.

The build files are therefore obsolete, and it is no longer necessary to keep them in the master branch of the repo.

Change

Remove the Node.js 18 directories:

• base-internal/releases/node-18
• browsers-internal/releases/node-18

and in the following documents, add a section "Obsolete Releases". Provide corresponding commit links where the Node.js 18 release information can be found in the git history:

• base-internal/base-internal/README.md
• browsers-internal/README.md

This does not affect the availability of the images themselves, if they are ever needed for regression testing or similar. The obsolete Node.js 18 internal Cypress Docker images remain published to Docker Hub Cypress.io in:

• cypress/base-internal
• cypress/browsers-internal

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

Preview

• https://github.com/MikeMcC399/cypress-docker-images/blob/remove/internal-node-18-builds/base-internal/README.md
• https://github.com/MikeMcC399/cypress-docker-images/blob/remove/internal-node-18-builds/browsers-internal/README.md

[jennifer-shehane]

Thanks for cleaning this up!

[MikeMcC399]

@jennifer-shehane

Thanks for cleaning this up!

Sure! I noticed when testing markdown-link-check that it was testing all these old files, so it seemed like a good opportunity to archive them.