Getting 404 while uploading package to JFrog artifactory

While uploading file to JFrog artifactory using Github Action we are getting 404. seems to it's appending "Build" metadata like "Build number, Build name " etc..

Here is the build log(uploading url):
https://artifactory.xyz.com/ext-release-local/xyz-CCPX/demo.env;build.number=33;build.timestamp=1659113030285;vcs.revision=35fdebe46da530800c16b011e2aba1756c2d6d6f;vcs.url=https%3A%2F%2Fgithub.com%2Fxyz-prod%2FCentralised-Config-Files.git;vcs.branch=master;build.name=Upload+Config+files+to+Artifactory:

Here is the workflow

name: Upload Config files to Artifactory

on:
push:
branches:
- master

workflow_dispatch:

jobs:
publish:
runs-on: [self-hosted, linux, X64]
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Setup Artifactory
uses: jfrog/setup-jfrog-cli@v2
- name: Upload to Artifactory
run: jf rt u --spec artifactory-spec.json --url 'https://artifactory.xyz.com' --user ${{ secrets.xyz_ARTIFACTORY_USER }} --password ${{ secrets.XYZ_ARTIFACTORY_PASS }}

Here is the spec file

{
"files": [
{
"pattern": "configs/*.env",
"target": "ext-release-local/xyz-CCPX/"
},
{
"pattern": "configs-tf/tf-apply.sh",
"target": "ext-release-local/xyz-CCPX/TF-CONFIG/"
}
]
}

How can we skip the build metadata during upload, like "build number, buildname" etc..

Start with the workflow and artifactory-spec.json shown in the report, then inspect how the Upload step invokes JFrog CLI and how build metadata is added to the upload URL. Reproduce the 404 with the supplied spec and determine whether the action or CLI configuration controls that metadata; done means a documented or verified way to upload without it.