[CI] Add multi-version smoke coverage for supported Python and Node baselines

[utksh1]

Summary

The docs mention supported Python and Node baselines, but CI currently exercises a single version of each runtime.

Scope

• Add lightweight matrix coverage for the officially supported baselines.
• Keep the matrix small enough to stay practical.
• Update contributor docs if the support policy changes.

Acceptance criteria

• CI exercises more than one supported runtime baseline where it matters.
• Runtime support claims are grounded in automation.
• The matrix remains maintainable.

[Rakshak05]

Hii @utksh1, i would like to work on this. Can you please assign it to me under GSSoC'26 contributor!?

[Apoorv-Raj777]

Hii @utksh1 , I would like to work on this. Can you please assign it to me under GSSoC'26 contributor!?

[anshul23102]

Interested in contributing to this under NSoC'26. This is a valuable issue addressing important functionality/quality. Happy to take this on.

/assign

[anshul23102]

Interested in contributing under NSoC'26. This is a valuable issue. Happy to work on it.

/assign

[nensii21]

@utksh1 /assign

[anshul23102]

Hi @utksh1 👋

I would like to work on this issue. This contribution is being made under NSoC'26 (Nexus Spring of Code 2026).

I have reviewed the issue and am ready to implement the solution. Could you please assign this to me?

Thank you!

[jyotsnak1603]

Hi @utksh1,

I would like to work on this issue under GSSoC 2026.

I reviewed the requirements and understand that the goal is to extend CI coverage by introducing a maintainable runtime matrix for the officially supported Python and Node.js baselines while keeping workflow execution practical. My approach would be to review the existing GitHub Actions workflows, identify the supported runtime versions from the project documentation, implement lightweight matrix testing, and verify that contributor documentation remains aligned with the supported versions.

I have experience working with CI/CD workflows, GitHub Actions, Docker, and automation pipelines, and I would be happy to contribute this enhancement. One of my project has complete use of workflows, GitHub Actions, Docker and Jenkins.

Could you please assign this issue to me?

Thank you.