Fix minor documentation build issues

Fix several redirects caught by a links check. Add new Pydantic
noise to nitpick_ignore.

CHANGELOG.md

@@ -86,7 +86,7 @@ Changes for the upcoming release can be found in [changelog.d](https://github.co
 
 ### Other changes
 
-- Safir now uses the [Ruff](https://beta.ruff.rs/docs/) linter instead of flake8 and isort.
+- Safir now uses the [Ruff](https://docs.astral.sh/ruff/) linter instead of flake8 and isort.
 
 <a id='changelog-4.3.1'></a>
 ## 4.3.1 (2023-07-17)

docs/documenteer.toml

@@ -19,6 +19,7 @@ nitpick_ignore_regex = [
 nitpick_ignore = [
     ['py:class', 'unittest.mock.Base'],
     ['py:class', 'unittest.mock.CallableMixin'],
+    ["py:obj", "ComputedFieldInfo"],
     ["py:obj", "JobMetadata.id"],
     ["py:class", "pydantic.BaseModel"],
     ["py:class", "BaseModel"],

docs/user-guide/set-up-from-template.rst

@@ -109,15 +109,15 @@ Now `create your application's repository on GitHub <https://docs.github.com/en/
 The first push to GitHub will fail.
 That's because the Docker build step doesn't credentials for Docker Hub.
 
-To set those credentials, follow GitHub's help page `Creating and storing encrypted secrets <https://docs.github.com/en/actions/security-guides/encrypted-secrets>`__.
+To set those credentials, follow GitHub's help page `Creating and storing encrypted secrets <https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions>`__.
 The variables are:
 
 ``DOCKER_USERNAME``
     A Docker Hub username that has access to the lsstsqre organization on Docker Hub.
 
 ``DOCKER_TOKEN``
     A Docker Hub Personal Access Token associated with ``DOCKER_USERNAME``.
-    `Create a dedicated token <https://docs.docker.com/docker-hub/access-tokens/>`__ specifically for your project's GitHub Actions workflow.
+    `Create a dedicated token <https://docs.docker.com/security/for-developers/access-tokens/>`__ specifically for your project's GitHub Actions workflow.
 
 After setting these secrets, re-run the GitHub Action by `re-running the workflow job from the GitHub Actions UI <https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs>`__ or by pushing a new commit to GitHub.