Update default JFrog CLI version to 2.90.0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 266
- Forks
- 110
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
The current default version (2.88.0) causes CI/CD pipeline failures when using Maven Docker images with floating tags like maven:3-amazoncorretto-25-al2023. This was fixed in jfrog-cli v2.90.0.
Describe the solution you'd like to see
Update the default version in action.yml from 2.88.0 to 2.90.0:
inputs:
version:
description: "JFrog CLI Version"
default: "2.90.0"
required: false
Describe alternatives you've considered
-
Pin the Maven image to a specific tag:
container: maven:3.9.11-amazoncorretto-25-al2023 -
Explicitly specify the CLI version in every workflow:
- uses: jfrog/setup-jfrog-cli@v4 with: version: 2.90.0
Both work but require changes to existing workflows.
Additional context
- Fix released in: https://github.com/jfrog/jfrog-cli/releases/tag/v2.90.0
- Tested and confirmed working with
version: 2.90.0andversion: latest
Contributor guide
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.
Research direction
Open action.yml and locate the inputs.version definition. Update the default from 2.88.0 to 2.90.0, then verify the file retains the requested input description and optional setting; done means new workflows use JFrog CLI 2.90.0 by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100