Skip to content

[TS-192] Monorepo prefix does not pick up last version. #81

@Gander7

Description

@Gander7

Scenario, A repo with multiple libraries within (one per folder)

  • Library1/
  • Library2/
  • Library3/

I already have the following tags on the relevant commits for each version. These pre-existed using git-version and were done manually.

  • Library1/v1.0.1

  • Library1/v1.0.0

  • Library2/v1.0.0

  • Library3/v1.0.0

  • Library3/v1.1.0

  • Library3/v1.1.1

I'm trying to implement git-version to get the next version for Library3.

    - name: Git Version
      uses: codacy/[email protected]
      with:
        log-paths: Library3/
        prefix: Library3/v

It attempts to version Library3 as v0.0.1

Run codacy/[email protected]
Run set -eo pipefail
Run set -eo pipefail
Previous Version: Library3/v0.0.0
Run set -eo pipefail
New Version: Library3/v0.0.1-testbranch.1.bb3d664

Expected: That the Previous version is detected as Library3/v1.1.1 and the new version should start with Library3/v1.1.2

I'm not sure if git-version just looks at the last tag, this may or may not be the last version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    jira-issueIssue tracked on JIRA

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions