ACTION NEEDED
Lance follows the Conventional Commits specification for release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.

For details on the error please inspect the "PR Title Check" action.

Code Review

P0 - Ambiguity between tags and branches without "/":

The FromStr implementation uses the presence of / to distinguish between branches and tags when there is no : separator. This creates an ambiguity: how would a user specify a branch named "feature" (no slash) vs a tag named "feature"?

Currently "tag1".parse::<Ref>() returns Tag("tag1"), but there is no way to parse a branch name without a slash (e.g., "dev" branch) unless using the colon syntax ("dev:").

Consider either:

1. Documenting this limitation clearly
2. Requiring explicit syntax for disambiguation (e.g., tag:name vs branch:name)
3. Adding methods like Ref::parse_as_branch() / Ref::parse_as_tag() for explicit parsing

P1 - Inconsistency with existing From<&str> impl:

The existing From<&str> impl (line 46-49) unconditionally converts to Tag:

impl From<&str> for Ref {
    fn from(reference: &str) -> Self {
        Tag(reference.to_string())
    }
}

But FromStr has different behavior - "42".parse::<Ref>() returns VersionNumber(42) while Ref::from("42") returns Tag("42"). This inconsistency could cause subtle bugs. Consider deprecating or removing the From<&str> impl, or documenting the behavioral difference prominently.

Codecov Report

❌ Patch coverage is 78.72340% with 10 lines in your changes missing coverage. Please review.

📢 Thoughts on this report? Let us know!

I'd +1 the automated code review concern here: how do we differentiate from branches? We can maybe add some additional rules for what is a valid tag. It seems like this might be worth designing the API in an issue first before going into implementation.

There any background on this feature? Why did you decide to implement it?