GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — chore(deps): update dependency yaml to v2.9.1 by renovate[bot] · Pull Request #54 · DUpdateSystem/docs

Conversation

@renovate

@renovate renovate Bot commented May 11, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yaml (source) 2.8.4 → 2.9.1 age adoption passing confidence

Release Notes

eemeli/yaml (yaml)

v2.9.1

Compare Source

  • Limit recursive merge aliases (#​685, #​713)
  • Simplify line unfolding during quoted string parsing (#​714)

v2.9.0

Compare Source

The changes here are really only patches, but I'm releasing this as a minor version to note a small change to the documentation of parseDocument() and parseAllDocuments(): I've removed the claim that they'll "never throw".

It remains the case that practically all non-malicious inputs will be handled without emitting an error, but there is a decent chance that code paths remain where e.g. a RangeError due to call stack exhaustion can be triggered by malicious inputs. Up to now, I've considered these as security vulnerabilities, and in fact it's the only category of error for which yaml CVEs have been issued so far.

Starting from this release, I'll be considering such errors as bugs, but not vulnerabilities. I do welcome people and/or LLMs looking for them, but please report them as normal issues rather than suspected security vulnerabilities. This also applies to previously undiscovered bugs in earlier releases.

  • fix: Avoid calling Array.prototype.push.apply() with large source array
  • fix(lexer): Avoid recursive calls that may exhaust the call stack

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from d450c6b to ef59273 Compare May 28, 2026 16:55
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from ef59273 to af388e6 Compare June 11, 2026 11:13
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from af388e6 to 61146a3 Compare July 12, 2026 10:34
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from 61146a3 to d7db9ee Compare July 30, 2026 15:14
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from d7db9ee to f3b76f5 Compare September 7, 2026 15:47
@renovate renovate Bot changed the title chore(deps): update dependency yaml to v2.9.0 chore(deps): update dependency yaml to v2.9.1 Sep 12, 2026
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from f3b76f5 to 431a5e7 Compare September 12, 2026 00:43
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from 431a5e7 to ef9f41d Compare September 30, 2026 19:52
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from ef9f41d to dfbfbaa Compare October 20, 2026 09:54
@renovate
chore(deps): update dependency yaml to v2.9.1
7f86a8a
@renovate
renovate Bot force-pushed the renovate/yaml-2.x branch from dfbfbaa to 7f86a8a Compare November 11, 2026 12:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

0 participants

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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.