Repository navigation
chore(deps): bump js-yaml from 5.4.2 to 5.4.3 in the production-dependencies group - #440
Conversation
Bumps the production-dependencies group with 1 update: [js-yaml](https://github.com/nodeca/js-yaml). Updates `js-yaml` from 5.4.2 to 5.4.3 - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@5.4.2...5.4.3) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.4.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: production-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
d6f08fc
ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blockedHive flagged this PR (author @dependabot[bot], head
Hive did not add the |
|
Triage of the red js-yaml is a bundled runtime dependency since #411, so the bump changes Nothing in the repo fixes this; a maintainer needs to add those two Dependabot secrets (Settings → Secrets and variables → Dependabot) and re-run the workflow, or hand-push 🐝 Hive Agent: — hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
Signed-off-by: Jeffrey Sica <me@jeefy.dev>
Signed-off-by: Jeffrey Sica <me@jeefy.dev>
Signed-off-by: Jeffrey Sica <me@jeefy.dev>
|
The repack job built /kind cleanup |
github-actions
Bot
added
the
kind/cleanup
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
Bot
added
lgtm
The previous repack came from a node_modules that still held js-yaml 5.4.2; CI's fresh npm ci bundles 5.4.3 (#440), so the drift gate failed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Bob Killen <bkillen@linuxfoundation.org>
* feat(owners): support GitHub groups in OWNERS approvers and reviewers List a team of the repository's org as @org/team; its members are resolved through the teams API. Other orgs' groups are ignored. Hive-Run: #485 Hive-Plan: owners-github-groups Hive-Spec: owners#github-groups Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com> * fix(owners): warn once per group entry, skip team reads for direct listings - expandGroups warned on every call, and the per-file expansion calls it twice per changed file, so one foreign-org group in a root OWNERS file produced a warning per file per role. Warn once per entry per run. - An `@…` entry that is not `@<org>/<team-slug>` used to be kept as a literal login that can never match; drop it with a warning. - ownersInclude answers a directly listed login before reading any team, so the root-OWNERS authorization path makes no teams-API call in the common case. - Docs: the default GITHUB_TOKEN has no organization permissions, so groups need the `token` secret with Members: read; say so in commands, installing and the day-one surprises table, and point the OWNERS_ALIASES note at groups. - Tests: unit cases for the dedupe, the malformed entry, expandOwnersSet and ownersInclude; a bundle file driving all four arms through dist/index.js. dist/ repacked. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Bob Killen <bkillen@linuxfoundation.org> * chore: repack dist/ against the locked js-yaml 5.4.3 The previous repack came from a node_modules that still held js-yaml 5.4.2; CI's fresh npm ci bundles 5.4.3 (#440), so the drift gate failed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Bob Killen <bkillen@linuxfoundation.org> --------- Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com> Signed-off-by: Bob Killen <bkillen@linuxfoundation.org> Co-authored-by: mrbobbytables <mrbobbytables@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Bumps the production-dependencies group with 1 update: js-yaml.
Updates
js-yamlfrom 5.4.2 to 5.4.3Changelog
Sourced from js-yaml's changelog.
Commits
78326245.4.3 released0cbb471Fix whitespace-only block scalar followed by a less indented line, close #80230108ccParse the first block mapping key once (#800)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions