2.92.0 release cause 404 during go package upload

Open
#3,371 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, go
Domain
cli

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.

Description

bug
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

Dominant language
Go
Stars
595
Forks
307
Avg merge
4d 17h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jfrog/jfrog-cli

All issues in jfrog/jfrog-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.