'package version create' is failing for all Custom Metadata records with 'not found custommetadata__mdt'.

[good-ghost]

Note
Before you submit your issue, make sure that:

• You're using the latest version of Salesforce CLI.
• You've searched both open and closed issues for related posts.
• You've used the doctor command to diagnose common issues.
• You understand that GitHub Issues don't adhere to any agreement or SLA.
  • If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary

When I create package version, I met the messages something like followings.

It is similar problem like Issue #1582

MyCustom__mdt: Must specify a non-empty plural label for the CustomObject
MyCustom__mdt: My Custom Layout: Parent entity failed to deploy
MyCustom.RecordName: Custom metadata type MyCustom__mdt is not available in this organization.
MyHandleTriggerHandler: Invalid type: MyCustom__mdt

Steps To Reproduce

I cannot provide the codeset, it is company confidentials.

However, I was create a package version at 2024/11/25 with cli version 2.66.7. But it was failed at 2024/11/26 with cli version 2.66.7 and 2.67.7. I trying to package version create with almost same codeset. I just chaged a field size of string field of custom metadata. If I tried to restore the field to previous one, package version create still failed.

I also tried with version 2.68.6 right now, met the same result 'failed'

Expected result

Package version cretaed

Actual result

Failed package version create.

Additional information

System Information

OS : Windows 10
Terminal : PowerShell in VS Code

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.68.6",
  "nodeVersion": "node-v22.11.0",
  "osVersion": "Windows_NT 10.0.19045",
  "rootPath": "C:\\Util\\sf\\client",
  "shell": "powershell",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.10 (core)",
    "@oclif/plugin-commands 4.1.10 (core)",
    "@oclif/plugin-help 6.2.18 (core)",
    "@oclif/plugin-not-found 3.2.28 (core)",
    "@oclif/plugin-plugins 5.4.17 (core)",
    "@oclif/plugin-search 1.2.16 (core)",
    "@oclif/plugin-update 4.6.13 (core)",
    "@oclif/plugin-version 2.2.16 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.23 (core)",
    "@oclif/plugin-which 3.2.19 (core)",
    "@salesforce/cli 2.68.6 (core)",
    "apex 3.6.3 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.75 (core)",
    "data 3.11.4 (core)",
    "deploy-retrieve 3.15.13 (core)",
    "info 3.4.21 (core)",
    "limits 3.3.40 (core)",
    "marketplace 1.3.6 (core)",
    "org 5.2.4 (core)",
    "packaging 2.9.3 (core)",
    "schema 3.3.42 (core)",
    "settings 2.4.6 (core)",
    "sobject 1.4.46 (core)",
    "telemetry 3.6.23 (core)",
    "templates 56.3.30 (core)",
    "trust 3.7.43 (core)",
    "user 3.6.3 (core)"
  ]
}

[github-actions]

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.

[github-actions]

Hello @good-ghost 👋 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.
• Search GitHub for existing related issues.

Thank you!

[github-actions]

Hello @good-ghost 👋 None of the versions of sf you shared match the latest release.

Shared: 2.67.7
Latest: 2.68.6

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[iowillhoit]

Hello @good-ghost, so this just suddenly stopped working (even with the same version of the CLI)?

It seems likely that this is a server side bug, but could you please provide a little more information:

• Set the JSFORCE_LOG_LEVEL=DEBUG environment variable
• Then, re-run the command with the --dev-debug command

I am hoping that this will give us a bit more information to pass along.

[good-ghost]

Hello, @iowillhoit
I tried with same source code and same version of cli, updated version of cli including latest version. Only difference is date. I was created version at 2023/11/25 and failed from 2024/11/26.

Here is modre detail log file.
report.txt

BTW, If I skip the validation, package version would be created.

Thanks and regards.

[iowillhoit]

Thank you for the additional details @good-ghost! I have reached out to the Packaging team about this.

[iowillhoit]

Toward the end of that file there are several errors listed. Have you looked to try to resolve those? The errors could be cascading. I'd start by looking at Invalid type: AdvA_ApprovalTemplate__mdt.

If you are unable to resolve those errors, are you able to provide use with an sfdx project that reproduces this issue?

[good-ghost]

I can not resolve 'Invalid type error'. I was create a package version at 2024/11/25 with same source codes. I'm sorry, due to our confidentiality pledge, we can't share the code we're developing externally.