infochangedAtlassian calls it: Fixed
Linter behaviour fixed for manifest environment variables
- Announced
- Tags
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v2 - 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
- Update your Forge CLI to version 13.4.0 or later by running: ```
npm install -g @forge/cli@latest ```
- For more information on using variables in your manifest, see the manifest variables reference.
- To learn more about why these manifest checks and approvals are required, see the documentation on major version upgrades.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.