Update mkdesigner to 0.5.1

[BiocondaBot]

Update mkdesigner: 0.4.4 → 0.5.1

Info	Link or Description
Recipe	recipes/mkdesigner (click to view/edit other files)
Summary	Genome-wide design of markers for PCR-based genotyping from NGS data.
Home	https://github.com/KChigira/mkdesigner
Releases	https://pypi.org/pypi/mkdesigner/json
Recipe Maintainer(s)	@KChigira

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces several updates to the meta.yaml file for the mkdesigner package. The version number has been increased from 0.4.4 to 0.5.1, and the corresponding SHA256 checksum for the source tarball has been updated to ensure it matches the new version. The run_exports section has been modified to change the maximum pinning from max_pin="x" to max_pin="x.x". Additionally, setuptools has been added to the host requirements, indicating a dependency necessary for building the package. The about section has been adjusted to remove the trailing slash from the home URL, which now points to the GitHub repository. Furthermore, a new field named dev_url has been added to provide a direct link to the GitHub repository for development purposes. Overall, the structure of the meta.yaml file remains unchanged aside from these modifications.

Possibly related PRs

• Update dajin2 to 0.5.5 #51230: Updates the version and SHA256 checksum in the meta.yaml file, similar to the changes in the main PR for mkdesigner.
• Update snk-cli to 0.5.4 #51233: Reflects updates to the version and SHA256 checksum in the meta.yaml file, akin to the main PR.
• Update snk-cli to 0.5.5 #51265: Modifies the version and SHA256 checksum in the meta.yaml file for the snk-cli package, paralleling the main PR.
• Update sourcepredict to 0.5.1 #51388: Updates the version and SHA256 checksum in the meta.yaml file, mirroring the changes made in the main PR.
• Update biobb_cmip to 5.0.0 #51455: Includes an update to the version and SHA256 checksum in the meta.yaml file, similar to the updates in the main PR.
• Rebuild biobb_cp2k #51531: Changes the version and SHA256 checksum in the meta.yaml file, reflecting the updates made in the main PR.
• Update clinvar-this to 0.18.3 #51560: Updates the version and SHA256 checksum in the meta.yaml file, consistent with the changes in the main PR.
• Update pggb to 0.7.1 #51562: Involves updates to the version and SHA256 checksum in the meta.yaml file, similar to the updates in the main PR.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

recipes/mkdesigner/meta.yaml (1)

48-53: Consider consolidating redundant URLs

The home and dev_url fields currently point to the same GitHub repository. Consider either:

1. Removing the dev_url field since it's redundant, or
2. Using a different URL for one of the fields (e.g., PyPI page for home and GitHub for dev_url)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between cc53905 and 3a2c321.

📒 Files selected for processing (1)

• recipes/mkdesigner/meta.yaml (3 hunks)

🧰 Additional context used

🔇 Additional comments (5)

recipes/mkdesigner/meta.yaml (5)

2-2: LGTM: Version update matches PR objective

The version update from 0.4.4 to 0.5.1 is consistent with the PR description.

---

21-21: LGTM: Improved version pinning strategy

The change to max_pin="x.x" is a good practice as it provides stricter version control, ensuring better compatibility by preventing automatic updates to minor versions.

---

27-27: LGTM: Added required build dependency

The addition of setuptools to host requirements is appropriate as it's commonly needed for Python package builds.

---

Line range hint 1-59: LGTM: Well-structured package update

The package update is well-structured with:

• Appropriate version constraints for dependencies
• Comprehensive test coverage
• Proper license specification
• Clear maintenance information

🧰 Tools

🪛 yamllint

[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)

---

10-10: Verify SHA256 checksum authenticity

Let's verify that the SHA256 checksum matches the source tarball from PyPI.