2.92.0 release cause 404 during go package upload
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 307
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 17
Description
Describe the bug
Using in github actions:JFROG_CLI_USER_AGENT: setup-jfrog-cli-github-action/3.5.3
While running jf go-publish XYZ --build-name="XYZ" --build-number="XYZ"
i got:
response: 404
{
"errors" : [ {
"status" : 404,
"message" : "Not Found"
} ]
}
Current behavior
Jfrog is malforming url parameter added to PUT request:
vcs.url=https:/github.com/ABC/XYZ
with missing "/"
Reproduction steps
No response
Expected behavior
Upload package with 200 return code as it was in version 2.91.0
JFrog CLI version
2.92.0
Operating system type and version
Amazon Linux 2023.6.20241111
JFrog Artifactory version
7.84.20
JFrog Xray version
No response
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
Start with the jf go-publish upload path and compare URL handling between JFrog CLI 2.91.0 and 2.92.0. Reproduce the GitHub Actions upload using the reported vcs.url, then verify that it preserves https:// and the package upload returns HTTP 200.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100