Skip to content

Consider updating yawn-yaml to 3.0 in scaffolder-backend-module-utils #2144

@rmartine-ias

Description

@rmartine-ias

Feature Suggestion

We were having problems with the YAML merge action failing to preserve some comments. We opened a PR on the upstream repo fixing the issue: mohsen1/yawn-yaml#120. This was obviated by a complete rewrite of yawn-yaml a day or two later. The rewrite fixes this and other bugs. We've pinned our resolution of yawn-yaml to ^3 and it's working fine, and has resolved issues that we were having with the roadie yaml merge action. However, this change was large, done pretty quickly with AI assistance, and recent, so I think it's likely there are unexplored edge cases that might end up getting tripped if you update now. But, it would fix some bugs.

Possible Implementation

  • Update yawn-yaml to 3.0 in scaffolder-backend-module-utils
  • OR wait a bit for bugs to be shaken out, then update

Context

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions