ci: remove explicit 'latest' version settings for Python and Node.js

[hzhangxyz]

close: #194

[Copilot]

Pull request overview

This PR removes explicit version specifications (latest) for Python and Node.js from GitHub Actions workflow configurations. The intent appears to be to rely on runner defaults rather than explicitly specifying "latest" as the version.

Changes:

• Removed python-version: latest from actions/setup-python and astral-sh/setup-uv actions in build/publish jobs
• Removed node-version: latest (with and without quotes) from actions/setup-node in build/publish jobs
• Changes affect 7 workflow files across pytest, jest, egg, bnf, and docs workflows

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
.github/workflows/pytest.yml	Removed Python version specification from wheels and sdist build jobs
.github/workflows/jest.yml	Removed Node.js version specification from npm publishing job
.github/workflows/egg-pytest.yml	Removed Python version specification from build job
.github/workflows/egg-jest.yml	Removed Node.js version specification from npm publishing job
.github/workflows/docs.yml	Removed Node.js version specification from documentation build job
.github/workflows/bnf-pytest.yml	Removed Python version specification from build job
.github/workflows/bnf-jest.yml	Removed Node.js version specification from npm publishing job

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Removing the node-version specification makes the documentation build non-deterministic. Without an explicit version, actions/setup-node will use the runner's default Node.js version, which can change when GitHub updates their runners. This could lead to inconsistent documentation builds or build failures if the default version changes. Consider specifying a version explicitly (e.g., '20' or '22') to ensure reproducible builds.

Suggested change

	with:
	with:
	node-version: '20'

[Copilot]

Removing the python-version specification makes the build non-deterministic. Without an explicit version, astral-sh/setup-uv will use the system Python version, which can vary across runner updates. This could lead to inconsistent builds. Consider specifying a version explicitly (e.g., '3.11' or '3.12') or use a .python-version file to ensure reproducible builds.

Suggested change

	with:
	with:
	python-version: '3.12'

[Copilot]

Removing the node-version specification makes the npm publishing step non-deterministic. Without an explicit version, actions/setup-node will use the runner's default Node.js version, which can change when GitHub updates their runners. This could lead to inconsistent builds or publishing failures if the default version changes. Consider specifying a version explicitly (e.g., '20' or '22') to ensure reproducible builds.

Suggested change

	with:
	with:
	node-version: '22'

[Copilot]

Removing the python-version specification makes the build non-deterministic. Without an explicit version, actions/setup-python will use whatever Python version is pre-installed on the runner, which can vary across different runner images and change over time when GitHub updates their runners. This could lead to inconsistent builds and potential compatibility issues with cibuildwheel. Consider specifying a version explicitly (e.g., '3.11' or '3.12') or use a .python-version file to ensure reproducible builds.

Suggested change

	with:
	with:
	python-version: '3.12'

[Copilot]

Removing the python-version specification makes the build non-deterministic. Without an explicit version, astral-sh/setup-uv will use the system Python version, which can vary across runner updates. This could lead to inconsistent source distribution builds. Consider specifying a version explicitly (e.g., '3.11' or '3.12') or use a .python-version file to ensure reproducible builds.

Suggested change

	with:
	with:
	python-version: '3.12'

[Copilot]

Removing the node-version specification makes the npm publishing step non-deterministic. Without an explicit version, actions/setup-node will use the runner's default Node.js version, which can change when GitHub updates their runners. This could lead to inconsistent builds or publishing failures if the default version changes. Consider specifying a version explicitly (e.g., '20' or '22') to ensure reproducible builds.

Suggested change

	with:
	with:
	node-version: '22'

[Copilot]

Removing the python-version specification makes the build non-deterministic. Without an explicit version, astral-sh/setup-uv will use the system Python version, which can vary across runner updates. This could lead to inconsistent builds. Consider specifying a version explicitly (e.g., '3.11' or '3.12') or use a .python-version file to ensure reproducible builds.

Suggested change

	with:
	with:
	python-version: '3.12'

[Copilot]

Removing the node-version specification makes the npm publishing step non-deterministic. Without an explicit version, actions/setup-node will use the runner's default Node.js version, which can change when GitHub updates their runners. This could lead to inconsistent builds or publishing failures if the default version changes. Consider specifying a version explicitly (e.g., '20' or '22') to ensure reproducible builds.

Suggested change

	with:
	with:
	node-version: '20'