Update GitHub Pages dependencies: specify exact versions for improved…

[bolak92]

… stability

[Copilot]

Pull request overview

This PR attempts to improve stability by pinning exact versions for all GitHub Pages dependencies in the workflow, moving from flexible version constraints to fixed versions for packages like mkdocs, mkdocs-material, and their plugins.

Key Changes:

• Replaced the flexible pip install command with exact version pinning for all 11 dependencies
• Specified versions for core packages (mkdocs 1.6.1, mkdocs-material 8.2.7) and their dependencies

---

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

[Copilot]

Incorrect version specifier syntax for mike. The package uses mike=2.1.3 (single equals sign) instead of mike==2.1.3 (double equals sign). This will cause a syntax error when pip tries to install the dependencies.

Change mike=2.1.3 to mike==2.1.3 to match the correct pip version specifier format used for all other packages.

Suggested change

	pip install Markdown==3.10 Jinja2==3.1.6 pymdown-extensions==10.18 mkdocs==1.6.1 mkdocstrings==1.0.0 mkdocstrings-python==2.0.1 mike=2.1.3 mkdocs-autorefs==1.4.3 mkdocs-material==8.2.7 mkdocs-git-revision-date-localized-plugin==1.5.0 mkdocs-plugin-tags==1.0.2
	pip install Markdown==3.10 Jinja2==3.1.6 pymdown-extensions==10.18 mkdocs==1.6.1 mkdocstrings==1.0.0 mkdocstrings-python==2.0.1 mike==2.1.3 mkdocs-autorefs==1.4.3 mkdocs-material==8.2.7 mkdocs-git-revision-date-localized-plugin==1.5.0 mkdocs-plugin-tags==1.0.2

[bolak92]

@copilot
ERROR: Cannot install mike==2.1.3, mkdocs-autorefs==1.4.3, mkdocs-git-revision-date-localized-plugin==1.5.0, mkdocs-plugin-tags==1.0.2, mkdocs==1.6.1 and mkdocstrings==1.0.0 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
Error: Process completed with exit code 1.

[Copilot]

@bolak92 I've opened a new pull request, #4, to work on those changes. Once the pull request is ready, I'll request review from you.