Update fast-edit-distance to 1.2.2

[BiocondaBot]

Update fast-edit-distance: 1.2.1 → 1.2.2

Info	Link or Description
Recipe	recipes/fast-edit-distance (click to view/edit other files)
Summary	A implementation of edit distance with improved runtime.
Home	https://github.com/youyupei/fast_edit_distance
Releases	https://github.com/youyupei/fast_edit_distance/tags
Author	@youyupei

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the fast-edit-distance package. It increments the version from 1.2.1 to 1.2.2, updates the SHA256 checksum for the source tarball, and resets the build number from 2 to 0. The installation script remains unchanged.

Changes

Files	Change Summary
recipes/fast-edit-distance/meta.yaml	- Version updated from 1.2.1 to 1.2.2 - SHA256 checksum updated from c3f391...07247 to 71ead9...501 - Build number reset from 2 to 0

Possibly related PRs

• Update peaks2utr to 1.3.2 #50979: Updates the meta.yaml file for the peaks2utr package, including a version bump and SHA256 checksum update.
• Update straglr to 1.5.2 #51000: Modifies the meta.yaml file for the straglr package, with changes to the version number and SHA256 checksum.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4b6fcc8 and fb9d2f0.

📒 Files selected for processing (1)

• recipes/fast-edit-distance/meta.yaml (1 hunks)

🔇 Additional comments (4)

recipes/fast-edit-distance/meta.yaml (4)

2-2: Version update looks good.

The version bump from 1.2.1 to 1.2.2 aligns with the PR objectives and follows semantic versioning conventions for a patch update.

---

13-13: Build number reset is correct.

Resetting the build number to 0 for a new version is the correct approach. This ensures that build numbering starts fresh for version 1.2.2.

---

Line range hint 1-46: Overall recipe structure and updates look good.

The recipe has been correctly updated for the new version. All necessary changes have been made, including:

• Version update
• SHA256 checksum update
• Build number reset

The recipe structure follows Conda packaging best practices, and all sections (package, source, build, requirements, test, about, and extra) are properly configured.

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: SHA256 checksum update looks correct.

The SHA256 checksum has been updated, which is expected with a new version. This ensures the integrity and security of the package.

To verify the checksum, you can run the following script:

---

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.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.