I’m experiencing an issue with Forge lint and seeking guidance or insights to resolve it. Despite updating to the latest Forge CLI version, I still encounter a linting warning that I’m unable to resolve:
Warning: Could not perform some linting actions for PermissionLinter due to unhandled error "Unknown product".
Steps Taken:
Updated Forge CLI to the latest version.
Reviewed the manifest.yml for any apparent issues (provided below).
Ran forge lint --verbose, but it did not yield additional error details.
The manifest seems to be structured correctly, and the project is functioning as expected prior to this issue. I have not been able to isolate the cause of this warning and am unsure if it’s related to a specific configuration or a broader issue with the Forge platform.
Any insights, similar experiences, or suggestions for further troubleshooting would be greatly appreciated.
@Starware my understanding is that this is usually a project config issue - did you create your project using the Forge CLI? have you seen this error when the linter runs since you created your project or did it start happening after a change?
It started after a change, but it is there for a while. I had tought it is one of the temporariy errors by forge. But it stayed. I have removed everything except one module from the manifest.yml file, and it is still giving the same warning. –verbose flag doesn’t give any extra information.
forge lint --verbose
Warning: Your version of Forge CLI is out of date. We recommend you update to the latest version to get the latest features and bug fixes.
Run npm install -g @forge/cli@latest to update from version 12.6.1 to 12.7.0.
The linter checks the app code for known errors. Warnings are issues you should fix, but they won't stop the app code from building.
Press Ctrl+C to cancel.
Warning: Could not perform some linting actions for PermissionLinter due to unhandled error "Unknown product".
No issues found.
I ran into the same linting warning in my work. Having examined the issue the tech team & I found that the warning occurs in connection with a custom function in our resolvers named requestJiraPost which triggered a regex inside Forge linter that verifies “requestJira”, “requestConfluence”, and “requestBitbucket”. The idea is that it checks whether your function name contains one of those strings and then compares - if so you are getting this warning.
In my case, the Forge linter could not resolve my function, as a result, I got a warning until I simply renamed it from requestJiraPost → jiraPost (various combinations also worked as expected)
I suppose my case is directly related to your original problem.