infochangedAtlassian calls it: Fixed
Linter behaviour fixed for manifest environment variables
- Announced
- APIs
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3402
Forge CLI 13.3.0 introduced a server-side manifest check as part of the new approval workflow. However, environment variables in the manifest.yml file were not being interpolated before being sent to the validation endpoint. This caused the linter to return false-positive MANIFEST_INVALID_RULE errors for valid manifests.
This issue is fixed in Forge CLI 13.4.0. The CLI now correctly interpolates environment variables before performing the pre-deployment manifest check.
More details: [object Object]
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.