Disallow pre-release for uv

[ka-sarthak]

Summary by Sourcery

CI:

• Remove the "--prerelease=allow" flag from the uv run command in the mkdocs-deploy GitHub Actions workflow

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update the mkdocs-deploy workflow to disallow pre-release versions by removing the --prerelease=allow flag from the uv run command.

File-Level Changes

Change	Details	Files
Removed pre-release allowance from uv command in deployment workflow	Removed --prerelease=allow flag from uv run invocation	.github/workflows/mkdocs-deploy.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ka-sarthak - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[ka-sarthak]

We (with @DanielYang59) removed the Pydantic constraints in the dev table here, given that it was not being explicitly used in the package: #146. But doing so fails the mkdocs deployment.

I think the constraints were placed to avoid installing pre-release versions of Pydantic in the dev environment. But this would only happen if uv allows pre-release, which we do in mkdocs deploy CI. Do we need the pre-release flag in the first place? @hampusnasstrom, here you allowed the pre-release specifically in #139. Is this still required?

[hampusnasstrom]

I think that was just to get the macro from nomad-lab before it was in a official release. Should be safe to remove.