Skip to content

build(deps-dev): bump js-yaml from 4.3.1 to 4.3.2 in /frontend - #272

Merged
github-actions[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/frontend/js-yaml-4.3.2
Sep 9, 2026
Merged

build(deps-dev): bump js-yaml from 4.3.1 to 4.3.2 in /frontend#272
github-actions[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/frontend/js-yaml-4.3.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor

Bumps js-yaml from 4.3.1 to 4.3.2.

Changelog

Sourced from js-yaml's changelog.

4.3.2 - 2026-08-26

Changed

  • [backport] Hard-limit merge sequence size to 100.

Security

  • [backport] Count empty mappings in merge sequences toward maxTotalMergeKeys to limit CPU usage, #797.
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.1 to 4.3.2.
- [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.2/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.3.1...4.3.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.3.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: frontend. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 9, 2026
@github-actions
github-actions Bot merged commit 8dbf514 into master Sep 9, 2026
6 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/frontend/js-yaml-4.3.2 branch September 9, 2026 10:03
Sbussiso added a commit that referenced this pull request Sep 9, 2026
Four frontend bumps (#268, #270, #271, #272) merged to master this
morning and never deployed. Neither failure is obvious from the repo,
and CodeQL going green on those commits actively hides one of them.

GAP 1 — nothing gates the merge on CI. The workflow's own comment said
branch protection required "Backend tests" and "Frontend audit + build",
but master has no required status checks at all, so `gh pr merge --auto`
merges as soon as this workflow approves, with tests still running. The
comment described an intended state as though it were the current one.

Simply adding those required checks would make it worse: deploy.yml and
agent.yml are path-filtered, and a path-skipped workflow reports no
status, so a required check would hang every PR that misses its paths.
That needs an always-runs gate job, which is its own change.

GAP 2 — an auto-merged PR does not deploy. GitHub does not trigger
`on: push` workflows for pushes made with GITHUB_TOKEN, so master moves
and Test & Deploy never runs. Verified: those four merges produced zero
push-event runs. CodeQL ran anyway because it is GitHub "default setup"
(event `dynamic`), which is exactly why this looks fine at a glance.

The real fix for GAP 2 is merging with a PAT rather than GITHUB_TOKEN —
a credential decision, not mine to make unilaterally. Meanwhile
deploy.yml gets a workflow_dispatch trigger so undeployed commits can
be shipped without pushing an unrelated one on top.

Pushing this commit also deploys the four stranded bumps.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants