[ISSUE]: gittools/actions/gitversion/setup@v4 without inputs selects gitversion v7.x.x
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
Start with the gitversion/setup action and trace how it chooses a GitVersion.Tool version when no input is supplied; the issue does not name source files or tests. Reproduce the provided workflow and inspect the version selection against the enforced >=6.2.0 <7.0.0 range. Done means setup selects the highest in-range release, 6.8.2, without the range error.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have written a descriptive issue title
- I have searched issues to ensure it has not already been reported
GitVersion package
GitHub Actions
What are you seeing?
When using gittools/actions/gitversion/setup@v4 it selects the latest release that falls outside of the enforced range.
--------------------------
Acquiring GitVersion.Tool for version spec:
--------------------------
Querying tool versions for GitVersion.Tool
Found matching version: 7.0.0
Error: Version spec '' resolved as '7.0.0' does not satisfy the range '>=6.2.0 <7.0.0'.See https://github.com/GitTools/actions/blob/main/docs/versions.md for more information.
Error: Version spec '' resolved as '7.0.0' does not satisfy the range '>=6.2.0 <7.0.0'.See https://github.com/GitTools/actions/blob/main/docs/versions.md for more information.
What is expected?
That it would select the highest version within the range 6.8.2.
Steps to Reproduce
setup a github actions worklfow with
name: test
on: push
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: gittools/actions/gitversion/setup@v4
Output log or link to your CI build (if appropriate).
- Dominant language
- TypeScript
- Stars
- 274
- Forks
- 87
- Avg merge
- 20h 15m
- Merged PRs (30d)
- 45
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
approved check:passed streams:remove
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Monthly Not a priority
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Expensify/App#107229 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hiero-ledger/hiero-sdk-js#4793 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/vscode-cosmosdb#3594 · 1 comment ·
Maintainers usually reply within 1 day
-
bug priority: low role: BE stage: now
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ahmadrosid/nakama#2594 ·
Maintainers usually reply within 1 day