Skip to content

chore(deps): bump the frontend-npm group across 1 directory with 7 updates - #1230

Closed
dependabot[bot] wants to merge 8 commits into
developfrom
dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc
Closed

chore(deps): bump the frontend-npm group across 1 directory with 7 updates#1230
dependabot[bot] wants to merge 8 commits into
developfrom
dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor

Bumps the frontend-npm group with 7 updates in the /frontend directory:

Package From To
lucide-react 1.27.0 1.28.0
@playwright/test 1.62.0 1.62.1
@types/react 19.2.17 19.2.18
@types/react-dom 19.2.3 19.2.4
eslint 9.39.5 10.8.0
jsdom 30.0.0 30.0.1
postcss 8.5.18 8.5.25

Updates lucide-react from 1.27.0 to 1.28.0

Release notes

Sourced from lucide-react's releases.

Version 1.28.0

What's Changed

Full Changelog: lucide-icons/lucide@1.27.0...1.28.0

Commits

Updates @playwright/test from 1.62.0 to 1.62.1

Release notes

Sourced from @​playwright/test's releases.

v1.62.1

Bug Fixes

  • #41989 [Regression]: tsconfig "extends" bare specifier isn't resolved via node_modules walk-up like tsc (fatal since 1.62)
  • #41998 [Regression]: directory-form tsconfig project references ("path": "../pkg") fail to resolve (fatal since 1.62)
  • #41985 Accessibility snapshot drops button name when text is nested inside spans with aria-hidden SVG
  • #42000 [Regression]: page.evaluate() arg of a branded primitive type (string & { brand }) no longer type-checks since 1.62
  • #42013 [BUG]Image-type actionable elements are not presented in the snapshot.
Commits
  • 26a9e47 cherry-pick(#42043): docs: release notes for v1.62 Python, Java, and .NET (#4...
  • 0a81d5d cherry-pick(#42040): docs(release-notes): mention the isolated headless clipb...
  • 8376826 cherry-pick(#42034): fix(aria): keep icon-only clickable elements in ai snaps...
  • 66c5cc9 chore: mark v1.62.1 (#42020)
  • 9672bc3 cherry-pick(#42009): fix(types): support branded primitives in evaluate argum...
  • 4325804 cherry-pick(#41988): fix(aria): preserve names from collapsed text contributors
  • 9632f8e cherry-pick(#42005): fix(tsconfig): do not throw when "extends"/"references" ...
  • See full diff in compare view

Updates @types/react from 19.2.17 to 19.2.18

Commits

Updates @types/react-dom from 19.2.3 to 19.2.4

Commits

Updates eslint from 9.39.5 to 10.8.0

Release notes

Sourced from eslint's releases.

v10.8.0

Features

  • 2fee9bb feat: export ConfigObject from eslint/config (#21082) (sethamus)

Bug Fixes

  • 6b8d2f7 fix: escape reserved characters in rule id in html formatter (#21129) (Francesco Trotta)
  • 9091071 fix: prevent no-unreachable-loop crash when all loop types are ignored (#21116) (Pixel)
  • e23fafe fix: prefer-object-spread add semicolon when adding parenthesis (#21081) (synthex-byte)
  • 20b5ad0 fix: quadratic-time regex in prefer-template (#21096) (Milos Djermanovic)
  • 8b6f6c0 fix: apply ignore configs to computed methods in class-methods-use-this (#21094) (Pixel)
  • b2c608c fix: NewExpression with parenthesized callee in preserve-caught-error (#21083) (Francesco Trotta)

Documentation

  • 6ddf858 docs: fix broken Specify Parser Options anchor link (#21106) (Minsu)
  • 784dfbe docs: Clarify no-eq-null description (#21120) (Park Harin)
  • 7ec733a docs: Fix typos and grammar in glossary (#21095) (Marry (Subin Yang))
  • 92bb13f docs: replace quake link (#21108) (Jung Hyeon Jun)
  • 68eb4a5 docs: fix broken Specify Globals anchor links in rule pages (#21103) (Minsu)
  • d28f697 docs: replace Code Climate CLI links with Qlty CLI links (#21099) (Jung Hyeon Jun)
  • eccc68d docs: correct --suppressions-location option description (#21093) (Ga eun Lee)
  • c5963f7 docs: Update README (GitHub Actions Bot)

Chores

  • 4fbf46d test: pin webpack version to 5.108.4 (#21137) (Francesco Trotta)
  • 2d063e2 chore: update HTTP URLs to HTTPS in JSDoc and comments (#21101) (Bo Hyun Kim)
  • eccbe7b test: add error locations to no-class-assign (#21123) (devoil)
  • e7d1e43 ci: bump actions/setup-go from 6 to 7 (#21118) (dependabot[bot])
  • e9d66d0 ci: bump actions/setup-node from 6 to 7 (#21119) (dependabot[bot])
  • ee225b6 test: Add error location details to no-eq-null rule (#21117) (Park Harin)
  • 044a627 chore: update minimatch to ^10.2.5 (#21107) (김채영)
  • fb09aa8 chore: update ecosystem plugins (#21115) (ESLint Bot)
  • 5abd878 test: add error locations to no-proto (#21114) (Gihyeon Jeong / 정기현)
  • 9715887 test: Add error location details to no-div-regex (#21110) (Park Harin)
  • a746ec6 test: add error locations to no-new-wrappers (#21109) (Gihyeon Jeong / 정기현)
  • 8dde645 test: add error locations to no-ex-assign (#21102) (devoil)
  • 13ab0ec test: add error locations to no-label-var (#21098) (Gihyeon Jeong / 정기현)
  • a99906f test: Add error location details to no-delete-var rule (#21105) (Park Harin)
  • c47e8dc chore: add missing backticks to languages/js/index.js (#21104) (beeen)
  • 0174428 chore: add missing backticks to translate-cli-options.js (#21097) (dongkyu lee)
  • 3d36589 chore: add missing backticks to serialization.js (#21091) (이규환)
  • dcc9312 test: add error locations to eqeqeq (#21090) (Ga eun Lee)
  • 2710b18 ci: Add explicit permissions to rebuild-docs-sites workflow (#21089) (Marry (Subin Yang))
  • 5d2f866 chore: update dependency prettier to v3.9.5 (#21086) (renovate[bot])
  • d584e31 chore: fix failing ecosystem test for eslint-plugin-unicorn (#21084) (Francesco Trotta)
  • bf3eda0 chore: update ecosystem plugins (#21079) (ESLint Bot)

v10.7.0

Features

  • cf2a9bf feat: add errorClassNames option to preserve-caught-error rule (#21032) (sethamus)
  • f8b873a feat: max-nested-callbacks option for constructor callbacks (#21063) (fnx)

... (truncated)

Commits

Updates jsdom from 30.0.0 to 30.0.1

Release notes

Sourced from jsdom's releases.

v30.0.1

  • Fixed getComputedStyle() with calc() and other functions throwing an exception, which regressed in v30.0.0. (@​asamuzaK)
  • Sped up up range operations on large documents (@​leonidaz)
Commits
  • 6584485 30.0.1
  • 0c51df6 Update dependencies and dev dependencies
  • 32adb34 Bump @​asamuzakjp/dom-selector
  • 70f014a Speed up range operations on large documents
  • 250d7ee Partially fix getComputedStyle with calc()
  • See full diff in compare view

Updates postcss from 8.5.18 to 8.5.25

Release notes

Sourced from postcss's releases.

8.5.25

  • Fixed 8.5.17 visitor regression.
  • Fixed list.split() for non-string values (by @​amir-rezaei).

8.5.24

  • Preserve the BOM after the processing (by @​hdimer).

8.5.23

  • Do not load source map without opts.from for security reasons.

8.5.22

8.5.21

8.5.20

8.5.19

  • Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).
Changelog

Sourced from postcss's changelog.

8.5.25

  • Fixed 8.5.17 visitor regression.
  • Fixed list.split() for non-string values (by @​amir-rezaei).

8.5.24

  • Preserve the BOM after the processing (by @​hdimer).

8.5.23

  • Do not load source map without opts.from for security reasons.

8.5.22

8.5.21

8.5.20

8.5.19

  • Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).
Commits

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 <dependency name> major version will 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 version will 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

Summary by CodeRabbit

  • Chores
    • Updated frontend tooling and UI library dependencies.
    • Refreshed package resolution settings for improved consistency.
    • Updated PostCSS and Playwright versions.
    • Added automated validation for frontend quality checks and production builds.
    • Improved dependency governance and consistency across frontend development workflows.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 3, 2026
@dependabot
dependabot Bot requested a review from seonghobae as a code owner August 3, 2026 23:59
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 3, 2026
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Frontend dependency constraints were updated for lucide-react, @playwright/test, and postcss. A temporary GitHub Actions workflow now updates PostCSS governance references, validates frontend and backend checks, then commits and pushes the verified change before deleting itself.

Changes

Frontend governance repair

Layer / File(s) Summary
Update frontend dependency constraints
frontend/package.json, frontend/pnpm-workspace.yaml
Updates lucide-react to ^1.28.0, @playwright/test to ^1.62.1, and postcss to 8.5.25 across dependency settings and overrides.
Validate the exact-head governance change
.github/workflows/pr-1230-finalize-frontend-governance.yml
Checks out the triggering commit, updates stale PostCSS references, verifies the dependency closure, and runs frontend and backend validation.
Commit and push the verified change
.github/workflows/pr-1230-finalize-frontend-governance.yml
Deletes the temporary workflow, validates the staged changes, commits them, and pushes to the target branch.

Estimated code review effort: 4 (Complex) | ~45 minutes

Suggested labels: github_actions

Suggested reviewers: seonghobae

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the frontend dependency update and matches the seven dependency changes described in the objectives.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

PR governance metadata gate is not ready for b44d5f776c40a7248c3ee95d49f80cea655f301e:

  • Review decision is CHANGES_REQUESTED; address requested changes before merge.
  • Required check backend (Python 3.14) is FAILURE on the current head.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/package.json`:
- Line 45: Update the postcss workspace override in pnpm-workspace.yaml to
8.5.25, regenerate and commit the corresponding pnpm-lock.yaml, then verify the
dependency resolution with a frozen install using pnpm 11.5.3.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ffef09f-658c-47f2-bd50-76912447084c

📥 Commits

Reviewing files that changed from the base of the PR and between 0484ac3 and 93a7970.

⛔ Files ignored due to path filters (1)
  • frontend/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • frontend/package.json

Comment thread frontend/package.json
@seonghobae
seonghobae marked this pull request as draft August 4, 2026 00:08

Copy link
Copy Markdown
Contributor

@jules Repair this Dependabot group in place without adding workflow files and without merging it.

The current diff is not merge-ready: it still raises ESLint from 9.39.5 to 10.8.0, and it updates PostCSS only in package.json while the pnpm workspace's effective override remains 8.5.18. Treat current develop as the compatibility boundary.

Required final state:

  1. Keep ESLint on the latest compatible 9.x release; do not migrate to ESLint 10 in this dependency PR.
  2. Keep TypeScript on the existing 6.x line; do not broaden or opportunistically change the TypeScript/typescript-eslint compatibility surface.
  3. Preserve the compatible lucide-react, Playwright, React type, jsdom, and PostCSS updates when their tests pass.
  4. Set PostCSS to exactly 8.5.25 in the direct dependency and frontend/pnpm-workspace.yaml override, regenerate frontend/pnpm-lock.yaml with the repository-pinned pnpm version, and remove the redundant/ineffective resolutions.postcss entry. Do not leave two conflicting package-manager control planes.
  5. Prove the resolved package with pnpm exec node -p 'require("postcss/package.json").version' and pnpm why postcss; the resolved version must be exactly 8.5.25.
  6. Run pnpm test, pnpm lint, pnpm typecheck, and POSTCSS_WORKERS=1 DISABLE_POSTCSS_WORKERS=true pnpm build from frontend.
  7. Keep the final diff limited to frontend/package.json, frontend/pnpm-workspace.yaml, and frontend/pnpm-lock.yaml. Update the PR body version table and verification to match the exact head.

Leave the PR draft if any peer/dependency incompatibility or test failure remains. Otherwise mark it ready for independent review, but do not merge it.

coderabbitai[bot]
coderabbitai Bot previously approved these changes Aug 4, 2026
@seonghobae
seonghobae marked this pull request as ready for review August 4, 2026 07:16
@seonghobae
seonghobae force-pushed the dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc branch from e28e5ee to 6cd0d35 Compare August 4, 2026 07:31
@github-actions
github-actions Bot force-pushed the dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc branch from 6cd0d35 to 00397fe Compare August 4, 2026 07:46

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/pnpm-workspace.yaml`:
- Line 18: Update the expected PostCSS version values in the governance checks
within test_release_governance.py from 8.5.24 to 8.5.25, while preserving the
existing resolutions.postcss requirement.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 02fee735-cca4-4b6b-b9d0-9f4d5c4941a1

📥 Commits

Reviewing files that changed from the base of the PR and between 93a7970 and 00397fe.

⛔ Files ignored due to path filters (1)
  • frontend/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • frontend/package.json
  • frontend/pnpm-workspace.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • frontend/package.json

Comment thread frontend/pnpm-workspace.yaml

Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot @github

dependabot Bot commented on behalf of github Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

Comment thread .github/workflows/pr-1230-finalize-frontend-governance.yml Fixed

Copy link
Copy Markdown
Contributor

@opencode-agent @cwl-noema-review @coderabbitai review

Review exact current head only. Verify pnpm lock reproducibility, PostCSS security override alignment, supported ESLint/Next.js compatibility, frozen install, tests, lint, typecheck, coverage, production build, and absence of unrelated dependency or credential changes.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor
🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== PR metadata ==='
gh pr view 1230 --repo ContextualWisdomLab/naruon \
  --json number,state,isDraft,baseRefName,headRefName,headRefOid,title,body,files \
  --jq '{number,state,isDraft,baseRefName,headRefName,headRefOid,title,body,files:[.files[].path]}'

echo '=== exact changed files and diff stat ==='
git diff --name-status origin/develop...HEAD
git diff --stat origin/develop...HEAD

echo '=== exact dependency diff ==='
git diff --no-ext-diff --unified=80 origin/develop...HEAD -- \
  frontend/package.json frontend/pnpm-workspace.yaml frontend/pnpm-lock.yaml

echo '=== package manager and frontend metadata candidates ==='
fd -HI '^(package\.json|pnpm-workspace\.yaml|pnpm-lock\.yaml|\.npmrc|packageManager|volta)$' . \
  -E node_modules -E .git | sort

echo '=== root package manager fields ==='
if [ -f package.json ]; then
  jq '{packageManager,engines,volta}' package.json
fi

echo '=== frontend package scripts and dependency control fields ==='
jq '{packageManager,engines,scripts,dependencies,devDependencies,pnpm,resolutions,overrides}' frontend/package.json

echo '=== frontend workspace override configuration ==='
cat frontend/pnpm-workspace.yaml

echo '=== postcss and eslint lockfile occurrences ==='
rg -n -C 3 '(^\s{0,2}(postcss|eslint)@|^\s{2,}(postcss|eslint):|postcss@8\.5\.25|eslint@)' frontend/pnpm-lock.yaml

echo '=== dependency and credential indicators in the changed files ==='
git diff --no-ext-diff origin/develop...HEAD -- \
  frontend/package.json frontend/pnpm-workspace.yaml frontend/pnpm-lock.yaml \
  | rg -n -i -C 2 '(token|secret|password|api[_-]?key|authorization|npmrc|registry|https?://)' || true

Length of output: 116820


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== added workflow with line numbers ==='
nl -ba .github/workflows/pr-1230-finalize-frontend-governance.yml

echo '=== workflow credential and privilege indicators ==='
rg -n -i -C 3 '(permissions:|id-token|secrets\.|github\.token|GITHUB_TOKEN|token|write-all|contents:\s*write|pull-requests:\s*write|actions:\s*write|checkout@|curl|wget|gh\s)' \
  .github/workflows/pr-1230-finalize-frontend-governance.yml || true

echo '=== exact PR body dependency-table rows ==='
gh pr view 1230 --repo ContextualWisdomLab/naruon --json body --jq '.body' \
  | sed -n '/| Package | From | To |/,/^$/p'

echo '=== changed-line locations in manifest ==='
git diff --unified=0 origin/develop...HEAD -- frontend/package.json frontend/pnpm-workspace.yaml \
  | rg -n -C 2 '^[@+ -]' || true

Length of output: 1196


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== added workflow with line numbers ==='
awk '{printf "%6d  %s\n", NR, $0}' .github/workflows/pr-1230-finalize-frontend-governance.yml

echo '=== workflow credential and privilege indicators ==='
rg -n -i -C 3 '(permissions:|id-token|secrets\.|github\.token|GITHUB_TOKEN|token|write-all|contents:\s*write|pull-requests:\s*write|actions:\s*write|checkout@|curl|wget|gh\s)' \
  .github/workflows/pr-1230-finalize-frontend-governance.yml || true

echo '=== exact PR body dependency-table rows ==='
gh pr view 1230 --repo ContextualWisdomLab/naruon --json body --jq '.body' \
  | sed -n '/| Package | From | To |/,/^$/p'

echo '=== changed-line locations in manifest ==='
git diff --unified=0 origin/develop...HEAD -- frontend/package.json frontend/pnpm-workspace.yaml \
  | rg -n -C 2 '^[@+ -]' || true

Length of output: 7478


@seonghobae Review complete for head eb9e0442d45e7570e50739efc11cbcc627bc16c6.

Findings

  1. High — Remove the added workflow.
    .github/workflows/pr-1230-finalize-frontend-governance.yml is outside the required three-file frontend scope. It has contents: write permission, retains checkout credentials, modifies backend/tests/test_release_governance.py, commits, and pushes to the Dependabot branch. This violates the explicit requirement to add no workflow files and to avoid unrelated changes.

  2. Medium — Remove resolutions.postcss from frontend/package.json.
    The package file still contains resolutions.postcss: "8.5.25". The pnpm workspace override is the effective control plane. Keeping both entries conflicts with the requested removal of the redundant resolution.

  3. Medium — Update the PR body to match the exact head.
    The PR body still states that ESLint changes to 10.8.0 and that @types/react and @types/react-dom change versions. The current dependency diff retains ESLint 9.39.5 and does not change either React types package. The verification section also does not describe the exact current state.

Static verification

  • frontend/package.json, frontend/pnpm-workspace.yaml, and frontend/pnpm-lock.yaml align PostCSS at exactly 8.5.25.
  • The lockfile resolves one postcss@8.5.25 package. Next.js, Vite, and @tailwindcss/postcss use that version.
  • ESLint remains 9.39.5. This is compatible with the locked Next.js configuration.
  • TypeScript remains 6.0.3. The locked typescript-eslint range supports <6.1.0.
  • No credential values appear in the frontend dependency-file diff. The added workflow, however, uses write permission and persisted GitHub checkout credentials.

I could not run pnpm install --frozen-lockfile, tests, coverage, lint, typecheck, the PostCSS runtime checks, or the production build in this sandbox. CI must run these commands after the workflow is removed.

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

coderabbitai[bot]
coderabbitai Bot previously approved these changes Aug 7, 2026

Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot @github

dependabot Bot commented on behalf of github Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

Copy link
Copy Markdown
Contributor

/oc

Fix the sole exact-head Application CI failure directly on branch dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc; do not add a one-shot/self-mutating/branch-writer workflow.

Root cause from run 31151952069: all frontend tests, lint, production build, Playwright smoke, Docker validation, dependency review, Bandit, Semgrep, and Security Scan pass. The backend suite fails only because test_frontend_postcss_lock_is_cve_2026_69153_fixed hardcodes 8.5.24 while the valid dependency update moves every governed surface to 8.5.25.

Repair the governance test at the source rather than reverting the patched dependency:

  • derive governed_version from frontend/package.json devDependencies;
  • parse and require it to be at least (8, 5, 24), excluding the affected range while permitting later patched releases;
  • require package overrides, resolutions, pnpm-workspace.yaml, lockfile overrides, importer specifier/version, and the sole packages/snapshots PostCSS keys to equal that exact governed version;
  • retain exact single-version lock closure and reject drift or duplicate PostCSS versions;
  • update the docstring to describe affected-range exclusion plus exact cross-surface alignment.

Run the focused governance test, complete 1,600+ backend suite, frontend tests/lint/typecheck/build/Playwright smoke, dependency/security/container gates, and git diff --check. Keep the final diff limited to the Dependabot dependency surfaces plus the permanent governance test. Do not weaken lint, downgrade ESLint/PostCSS, or introduce temporary workflows.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/pr-1230-finalize-frontend-governance.yml:
- Around line 52-64: The workflow’s hardcoded replacement must be replaced by
permanent checks in test_release_governance.py. Update the governance tests to
derive the PostCSS version from frontend/package.json, require it to be at least
8.5.24, and verify exact alignment across the manifest, pnpm workspace override,
lockfile metadata, and the single-version lock closure; remove the temporary
"8.5.24" to "8.5.25" replacement step.
- Around line 84-109: Update the workflow’s verification steps before the
commit/push stage to run the repository’s required security scanners and
container checks as blocking gates. Add the established security and
container-check commands alongside the existing frontend and backend
verification commands, ensuring any failure stops the workflow.
- Around line 111-145: The workflow must not delete, commit, or push changes
from CI. Remove the self-mutating workflow file entirely, and apply the required
governance change directly to the Dependabot branch outside workflow automation.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6c3da85c-eca5-41a0-9739-04b86a406be1

📥 Commits

Reviewing files that changed from the base of the PR and between 00397fe and 7b592f5.

📒 Files selected for processing (1)
  • .github/workflows/pr-1230-finalize-frontend-governance.yml

Comment thread .github/workflows/pr-1230-finalize-frontend-governance.yml Outdated
Comment thread .github/workflows/pr-1230-finalize-frontend-governance.yml Outdated
Comment thread .github/workflows/pr-1230-finalize-frontend-governance.yml Outdated

Copy link
Copy Markdown
Contributor

/oc

Apply the PostCSS governance repair directly on exact head 8ab5896ea1bbed9e714b8752f9220feda030ffbb; the temporary branch-writer workflow has been removed and must not be recreated.

The dependency update itself is valid. Fix only backend/tests/test_release_governance.py:

  • derive the exact governed PostCSS version from frontend/package.json devDependencies.postcss;
  • parse it into exactly three decimal components and require it to be at least 8.5.24, thereby excluding CVE-2026-69153's affected range while allowing later patched releases;
  • require overrides, resolutions, pnpm-workspace.yaml overrides, lockfile overrides, root importer specifier/version, and the sole packages/snapshots PostCSS keys to equal that exact governed version;
  • retain the single-version lock-closure guarantee and reject any duplicate/drifted PostCSS version;
  • update the test docstring to state affected-range exclusion and exact cross-surface alignment, not one frozen historical patch.

Run the focused governance test, complete backend suite with warnings-as-errors, frontend tests/lint/typecheck/coverage/production build/Playwright smoke, dependency review, Bandit, Semgrep, Security Scan, container build, and git diff --check. Keep the final diff limited to the three Dependabot dependency files plus the permanent governance test. Do not reintroduce temporary workflows or downgrade any dependency.

Copy link
Copy Markdown
Contributor

@opencode-agent

Apply the remaining permanent governance repair directly to exact head 8ab5896ea1bbed9e714b8752f9220feda030ffbb on dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc. Do not add a temporary, one-shot, self-mutating, encoded-patch, or branch-writer workflow.

In backend/tests/test_release_governance.py, replace the hardcoded PostCSS 8.5.24 contract with a version-derived fail-closed contract:

  • read the exact governed version from frontend/package.json devDependencies.postcss;
  • require a strict major.minor.patch version and require it to be at least 8.5.24;
  • require overrides.postcss and resolutions.postcss in the package manifest to equal that exact governed version;
  • require frontend/pnpm-workspace.yaml overrides.postcss, lockfile overrides.postcss, and importer specifier/version to equal it;
  • require exactly one postcss@<governed-version> key in both lockfile packages and snapshots and reject any second PostCSS closure;
  • preserve the existing CVE-specific intent and public docstring.

Run the focused governance test, the complete backend suite, the complete frontend frozen-install/lint/type/test/coverage/build path with pnpm 11.5.3, repository security and container checks, docstring/coverage gates, and git diff --check. Push only the direct test-file change after successful verification. Then request fresh exact-head CodeRabbit/OpenCode review and resolve only findings demonstrably addressed by the new head. Do not approve, merge, release, or weaken branch protection.

Copy link
Copy Markdown
Contributor

@opencode-agent @cwl-noema-review

Exact-head repair request for b44d5f776c40a7248c3ee95d49f80cea655f301e against protected develop 5425ce4f55b2cf16b2c82a4fd661c9d0bd0660c7.

Application CI run 31177955666 is deterministically red only in test_frontend_postcss_lock_is_cve_2026_69153_fixed: the permanent governance test still hardcodes 8.5.24 while the reviewed frontend manifest/workspace/lock closure is now 8.5.25. Frontend CI, Security Scan, Dependency Review, Bandit, Semgrep, and container build are green on this exact head.

Repair this test contract directly on the existing branch, without any workflow writer. Preserve and strengthen the CodeRabbit-requested permanent behavior:

  • derive the governed PostCSS version from frontend/package.json rather than hardcoding 8.5.25;
  • parse the semantic version and require it to be at least 8.5.24 (the first governed CVE-2026-69153-safe floor);
  • require exact equality across devDependencies.postcss, overrides.postcss, resolutions.postcss, frontend/pnpm-workspace.yaml override, frontend/pnpm-lock.yaml override/importer metadata, and the unique postcss@<version> keys in both packages and snapshots;
  • preserve resolutions.postcss and pnpm 11.5.3 frozen-lock reproducibility;
  • rerun the focused governance test and complete backend/Application CI relevant tests before considering the repair complete.

Do not add or restore .github/workflows/pr-1230-finalize-frontend-governance.yml or any one-shot/self-mutating/write-capable workflow. Do not force-push, approve, merge, release, alter reviewer credentials, or weaken security/container gates. Refetch the exact live head before editing; if it moved from b44d5f776c40a7248c3ee95d49f80cea655f301e, abort stale work and re-plan.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head b44d5f776c40a7248c3ee95d49f80cea655f301e.

  • Head SHA: b44d5f776c40a7248c3ee95d49f80cea655f301e

  • Workflow run: 31189053425

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Frontend (3 files)"]
  S1 --> I1["browser runtime and bundle"]
  I1 --> R1["Review risk: Frontend (3 files)"]
  R1 --> V1["frontend tests"]
Loading

@opencode-agent

opencode-agent Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: b44d5f776c40a7248c3ee95d49f80cea655f301e
  • Workflow run: 31189053425
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head b44d5f776c40a7248c3ee95d49f80cea655f301e.

  • Head SHA: b44d5f776c40a7248c3ee95d49f80cea655f301e

  • Workflow run: 31189053425

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Frontend (3 files)"]
  S1 --> I1["browser runtime and bundle"]
  I1 --> R1["Review risk: Frontend (3 files)"]
  R1 --> V1["frontend tests"]
Loading

@dependabot @github

dependabot Bot commented on behalf of github Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Aug 10, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/frontend/frontend-npm-6c49e239bc branch August 10, 2026 02:58
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants