ci(plugins): fix build-plugin.yml release-notes block scalar indentation#1362
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
.github/workflows/build-plugin.ymlfails to parse:Invalid workflow file ... You have an error in your yaml syntax on line 279. Plugin releases (plugin-*-v*tags andworkflow_dispatch) can't run.The "Create GitHub Release" step builds
RELEASE_BODYas a multi-line shell string inside arun: |block scalar (indented 10 spaces). The string's continuation lines sat at column 0. A non-empty line dedented below the block indent ends the block scalar, so YAML tried to parsePlugin release for TablePro ...as structure and errored at line 279.Introduced by the pipeline rewrite in #1322 / #1343.
Fix
Indent the continuation lines to the block's 10-space indent so they stay inside the scalar. YAML strips the 10-space prefix, so the shell still receives clean column-0 markdown for the release notes.
Verified by parsing the full workflow with
yaml.safe_load(passes) and inspecting the renderedrunblock: the release-notes body has no leading whitespace.