Skip to content

Git tags for cross-ecosystem packages with the same name can conflict #239

@Princesseuh

Description

@Princesseuh

Describe the problem

In my repo, I have both a crate and a npm package with the same name, when creating Git tags Sampo does not disambiguate between them, causing a possible overlap if the versions ever conflict (in addition to just being confusing for users, really)

Image

Environment Information

uses: bruits/sampo/crates/sampo-github-action@main
Linux x64
Rust 1.94.1

What's the expected result?

Probably some sort of identifier when there is a possible conflict, so like if a repo has two packages of the same name, the git tags for those packages will always be package-ecosystem-version instead of just package-version?

Participation

  • I am willing to submit a pull request for this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2 - highBugs that violates the documented behavior.crt:sampo-coreChanges in Sampo core logic or internal utils.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions