build!: parse yaml with more strict multiline indentation rules#640
Merged
Conversation
🦋 Changeset detectedLatest commit: 7f55331 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Member
|
🏁 #637 |
aa572c8 to
1f588d1
Compare
Member
|
@dependabot recreate |
1f588d1 to
a99549e
Compare
a99549e to
caf399c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #640 +/- ##
=======================================
Coverage 99.86% 99.86%
=======================================
Files 8 8
Lines 731 731
=======================================
Hits 730 730
Misses 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Reference the s-flow-line-prefix(n) indentation rule so the breaking change points at the spec section that motivates it.
Illustrate the required indentation fix so readers can map the parsing error to the exact one-line change in their payload.
Correct "indentiation" and "compilant" so the release notes read cleanly.
Reword the line prefixes reference to lead into the illustrated fix instead of naming the raw production.
zimeg
approved these changes
Jul 15, 2026
zimeg
left a comment
Member
There was a problem hiding this comment.
🫡 @dependabot LGTM! The tests are passing and capture this expected behavior in a changeset for upcoming release 📚 ✨
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
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.
Bumps js-yaml from 4.2.0 to 5.2.1.
Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
ac16b425.2.1 released4a864e5Deps bump39f3211!!omap: addMapsupport and remove quadratic complexityff17f1eChangelog update8ed15f1deps bump1a562dcFix changelog linkc28ed5e5.2.0 released125cd5aAddmaxAliasesoption3105455ReplacemaxMergeSeqLengthoption withmaxTotalMergeKeys(more robust)39d00d6numbers: Drop boxed numbers support, simplify .identify() checks, clarify rou...