Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Gander7 opened this issue Jan 24, 2023 · 3 comments
Open

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

Gander7 opened this issue Jan 24, 2023 · 3 comments
Labels
jira-issue Issue tracked on JIRA

Comments

@Gander7
Copy link

Gander7 commented Jan 24, 2023

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.

@github-actions github-actions bot added the jira-issue Issue tracked on JIRA label Jan 24, 2023
@github-actions github-actions bot changed the title Monorepo prefix does not pick up last version. [TS-192] Monorepo prefix does not pick up last version. Jan 24, 2023
@github-actions
Copy link

Internal ticket created : TS-192

@Gander7
Copy link
Author

Gander7 commented Jan 24, 2023

This is also severely affected by #77.

@oleksandr-ivanov-ah
Copy link

I have created hotfix pr but it doesn't reviewed for months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira-issue Issue tracked on JIRA
Projects
None yet
Development

No branches or pull requests

2 participants