Skip to content

test: add isExactVersions tests#893

Merged
danielroe merged 1 commit intomainfrom
jg/test-semantically-nonsense
Feb 3, 2026
Merged

test: add isExactVersions tests#893
danielroe merged 1 commit intomainfrom
jg/test-semantically-nonsense

Conversation

@43081j
Copy link
Contributor

@43081j 43081j commented Feb 3, 2026

No description provided.

@vercel
Copy link

vercel bot commented Feb 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
npmx.dev Ready Ready Preview, Comment Feb 3, 2026 10:08pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
docs.npmx.dev Ignored Ignored Preview Feb 3, 2026 10:08pm
npmx-lunaria Ignored Ignored Feb 3, 2026 10:08pm

Request Review

@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 3, 2026

📝 Walkthrough

Walkthrough

A new exported function isExactVersion(version: string) was added to the versions utility module. The function validates whether a provided version string represents an exact version number. Accompanying test coverage was introduced in the test suite, verifying that the function returns true for exact stable and prerelease versions, and returns false for version ranges, dist-tags, and invalid strings. This addition expands the public API surface of the versions utility without modifying existing functionality.

🚥 Pre-merge checks | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request has no description provided by the author, making it impossible to assess whether the description relates to the changeset. Add a pull request description that explains the purpose, changes, and rationale for adding isExactVersion tests to help reviewers understand the intent.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch jg/test-semantically-nonsense

Comment @coderabbitai help to get the list of available commands and usage tips.

@danielroe danielroe enabled auto-merge February 3, 2026 22:09
@danielroe danielroe added this pull request to the merge queue Feb 3, 2026
Merged via the queue into main with commit c4755ed Feb 3, 2026
19 checks passed
@danielroe danielroe deleted the jg/test-semantically-nonsense branch February 3, 2026 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants