You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a multi-branch CI/CD pipeline. As of last week, we started seeing an error message around branch validation. Some of our packages were created with --branch tag some are not.
While trying to package metadata with a dependency on another package, we started seeing this error message:
No version number was found in Dev Hub for package id 0Ho08000000KymKCAS and branch undefined and version number 1.5.0.LATEST.
"branch undefined" section of this message is telling me that even though I didn't pass --branch tag while packaging, there is a branch validation happening to see if the dependent package was built on the same branch. This branch validation is new and it shouldn't be enforced.
{
"code": 1,
"context": "PackageVersionCreateCommand",
"commandName": "PackageVersionCreateCommand",
"message": "No version number was found in Dev Hub for package id 0Ho08000000KymKCAS and branch undefined and version number 1.5.0.LATEST.",
"name": "NoReleaseVersionFoundForBranchError",
"status": 1,
"stack": "NoReleaseVersionFoundForBranchError: No version number was found in Dev Hub for package id 0Ho08000000KymKCAS and branch undefined and version number 1.5.0.LATEST.\n at Messages.createError (/home/runner/sfdx/node_modules/@salesforce/core/lib/messages.js:393:16)\n at PackageVersionCreate.resolveBuildNumber (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:175:32)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async PackageVersionCreate.retrieveSubscriberPackageVersionId (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:108:37)\n at async Promise.all (index 2)\n at async PackageVersionCreate.createPackageVersionCreateRequestFromOptions (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:288:30)\n at async PackageVersionCreate.packageVersionCreate (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:477:25)\n at async PackageVersion.create (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersion.js:92:30)\n at async PackageVersionCreateCommand.run (/home/runner/sfdx/node_modules/@salesforce/plugin-packaging/lib/commands/package/version/create.js:60:24)\n at async PackageVersionCreateCommand._run (/home/runner/sfdx/node_modules/@oclif/core/lib/command.js:117:22)\n at async Config.runCommand (/home/runner/sfdx/node_modules/@oclif/core/lib/config/config.js:329:25)\n at async run (/home/runner/sfdx/node_modules/@oclif/core/lib/main.js:89:16)",
"exitCode": 1,
"warnings": []
}
The text was updated successfully, but these errors were encountered:
Hello @alper-tovi-cko 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).
A few more things to check:
Make sure you've provided detailed steps to reproduce your issue.
A repository that clearly demonstrates the bug is ideal.
Make sure you've installed the latest version of Salesforce CLI. (docs)
Better yet, try the rc or nightly versions. (docs)
Try running the doctor command to diagnose common issues.
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
Summary
We have a multi-branch CI/CD pipeline. As of last week, we started seeing an error message around branch validation. Some of our packages were created with --branch tag some are not.
While trying to package metadata with a dependency on another package, we started seeing this error message:
No version number was found in Dev Hub for package id 0Ho08000000KymKCAS and branch undefined and version number 1.5.0.LATEST.
"branch undefined" section of this message is telling me that even though I didn't pass --branch tag while packaging, there is a branch validation happening to see if the dependent package was built on the same branch. This branch validation is new and it shouldn't be enforced.
{
"code": 1,
"context": "PackageVersionCreateCommand",
"commandName": "PackageVersionCreateCommand",
"message": "No version number was found in Dev Hub for package id 0Ho08000000KymKCAS and branch undefined and version number 1.5.0.LATEST.",
"name": "NoReleaseVersionFoundForBranchError",
"status": 1,
"stack": "NoReleaseVersionFoundForBranchError: No version number was found in Dev Hub for package id 0Ho08000000KymKCAS and branch undefined and version number 1.5.0.LATEST.\n at Messages.createError (/home/runner/sfdx/node_modules/@salesforce/core/lib/messages.js:393:16)\n at PackageVersionCreate.resolveBuildNumber (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:175:32)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async PackageVersionCreate.retrieveSubscriberPackageVersionId (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:108:37)\n at async Promise.all (index 2)\n at async PackageVersionCreate.createPackageVersionCreateRequestFromOptions (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:288:30)\n at async PackageVersionCreate.packageVersionCreate (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersionCreate.js:477:25)\n at async PackageVersion.create (/home/runner/sfdx/node_modules/@salesforce/packaging/lib/package/packageVersion.js:92:30)\n at async PackageVersionCreateCommand.run (/home/runner/sfdx/node_modules/@salesforce/plugin-packaging/lib/commands/package/version/create.js:60:24)\n at async PackageVersionCreateCommand._run (/home/runner/sfdx/node_modules/@oclif/core/lib/command.js:117:22)\n at async Config.runCommand (/home/runner/sfdx/node_modules/@oclif/core/lib/config/config.js:329:25)\n at async run (/home/runner/sfdx/node_modules/@oclif/core/lib/main.js:89:16)",
"exitCode": 1,
"warnings": []
}
The text was updated successfully, but these errors were encountered: