Skip to content

build(deps): Bump the npm-dependencies group in /frontend with 3 updates - #3

Merged
alicoding merged 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/npm-dependencies-8f0be22188
Aug 12, 2026
Merged

build(deps): Bump the npm-dependencies group in /frontend with 3 updates#3
alicoding merged 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/npm-dependencies-8f0be22188

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the npm-dependencies group in /frontend with 3 updates: react-querybuilder, eslint-plugin-react-refresh and vite.

Updates react-querybuilder from 8.22.3 to 8.22.4

Release notes

Sourced from react-querybuilder's releases.

v8.22.4

Fixed

  • ValueEditor now assigns the rule's title to each input/selector of a between/notBetween bound pair, not just their wrapper element. Previously those controls had no accessible name, failing the WCAG level A label and select-name rules.

CHANGELOG entry for v8.22.4

react-querybuilder/react-querybuilder@v8.22.3...v8.22.4

Changelog

Sourced from react-querybuilder's changelog.

[v8.22.4] - 2026-08-07

Fixed

  • ValueEditor now assigns the rule's title to each input/selector of a between/notBetween bound pair, not just their wrapper element. Previously those controls had no accessible name, failing the WCAG level A label and select-name rules.
Commits

Updates eslint-plugin-react-refresh from 0.4.26 to 0.5.3

Release notes

Sourced from eslint-plugin-react-refresh's releases.

v0.5.3

  • Fix check for non component class exported via export { } #110 (fixes #109)

v0.5.2

  • Support nested function calls for extraHOCs (actually fixes #104)

v0.5.1

  • Mark ESLint v10 as supported
  • Support false positives with TypeScript function overloading (fixes #105)
  • Support nested function calls for extraHOCs (fixes #104)

v0.5.0

Breaking changes

  • The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
  • A new reactRefresh export is available and prefered over the default export. It's an object with two properties:
    • plugin: The plugin object with the rules
    • configs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.
  • customHOCs option was renamed to extraHOCs
  • Validation of HOCs calls is now more strict, you may need to add some HOCs to the extraHOCs option (like connect or styled)

Config example:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";
export default defineConfig(
/* Main config */
reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }),
);

Config example without config:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";
export default defineConfig({
files: ["/*.ts", "/*.tsx"],
plugins: {
// other plugins
"react-refresh": reactRefresh.plugin,
},
rules: {
// other rules
"react-refresh/only-export-components": [
"warn",
{ extraHOCs: ["someLibHOC"] },
</tr></table>

... (truncated)

Changelog

Sourced from eslint-plugin-react-refresh's changelog.

0.5.3

  • Fix check for non component class exported via export { } #110 (fixes #109)

0.5.2

  • Support nested function calls for extraHOCs (actually fixes #104)

0.5.1

  • Mark ESLint v10 as supported
  • Support false positives with TypeScript function overloading (fixes #105)
  • Support nested function calls for extraHOCs (fixes #104)

0.5.0

Breaking changes

  • The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
  • A new reactRefresh export is available and prefered over the default export. It's an object with two properties:
    • plugin: The plugin object with the rules
    • configs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.
  • customHOCs option was renamed to extraHOCs
  • Validation of HOCs calls is now more strict, you may need to add some HOCs to the extraHOCs option

Config example:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";
export default defineConfig(
/* Main config */
reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }),
);

Config example without config:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";
export default defineConfig({
files: ["/*.ts", "/*.tsx"],
plugins: {
// other plugins
"react-refresh": reactRefresh.plugin,
},
rules: {
</tr></table>

... (truncated)

Commits
  • 00818e9 v0.5.3 [publish]
  • 202fc4a Fix PascalCase class exported via export { Name } incorrectly treated as Re...
  • c0317bf Fix support for nested function calls for extraHOCs [publish]
  • 42a1805 Explicit v10 support (fixes #106) [publish]
  • 199793e Support nested function calls for extraHOCs (fixes #104)
  • 26b3c15 Support false positives with TypeScript function overloading (fixes #105)
  • daa2efb Revamp logic to catch more cases [publish] (#97)
  • See full diff in compare view

Updates vite from 8.2.0 to 8.2.1

Release notes

Sourced from vite's releases.

plugin-legacy@8.2.1

Please refer to CHANGELOG.md for details.

v8.2.1

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

8.2.1 (2026-08-06)

Bug Fixes

  • build: make client chunkImportMap work with sharedPlugins: true (#23184) (15f0307)
  • bundled-dev: inject client script tag before chunk scripts (#23161) (eac0cc8)
  • css: don't re-run lightningcss visitor during minify (fix #23146) (#23147) (de041a7)
  • deps: update all non-major dependencies (#23136) (14454fd)
  • deps: update rolldown-related dependencies (#23070) (7ac6f7f)
  • don't mutate the user config when resolving the lib entry from the top-level input (#23135) (b4bf596)
  • handle shebang ending with uncommon line terminators (#23038) (17f7b2f)
  • server: use a random port when port is 0 (#23158) (fddf4ea)

Performance Improvements

Documentation

  • build: fix incomplete @default for build.minify (#23177) (ef02435)

Miscellaneous Chores

  • deps: update dependency rolldown-plugin-dts to ^0.28.0 (#23137) (4adc1e7)
  • deps: update dependency strip-literal to v4 (#23140) (9db65ce)

Code Refactoring

  • bundled-dev: avoid injecting server values in the bundle (#22967) (23b8a08)
  • bundled-dev: remove rolldown lazy stub module workaround (#23129) (e72036e)

Tests

Commits
  • 4216158 release: v8.2.1
  • fddf4ea fix(server): use a random port when port is 0 (#23158)
  • de041a7 fix(css): don't re-run lightningcss visitor during minify (fix #23146) (#23147)
  • 15f0307 fix(build): make client chunkImportMap work with sharedPlugins: true (#23184)
  • c2155fe test(bundled-dev): enable sourcemap playgrounds (#23080)
  • ef02435 docs(build): fix incomplete @default for build.minify (#23177)
  • eac0cc8 fix(bundled-dev): inject client script tag before chunk scripts (#23161)
  • 23b8a08 refactor(bundled-dev): avoid injecting server values in the bundle (#22967)
  • e72036e refactor(bundled-dev): remove rolldown lazy stub module workaround (#23129)
  • 14454fd fix(deps): update all non-major dependencies (#23136)
  • Additional commits viewable in compare view

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

Bumps the npm-dependencies group in /frontend with 3 updates: [react-querybuilder](https://github.com/react-querybuilder/react-querybuilder/tree/HEAD/packages/react-querybuilder), [eslint-plugin-react-refresh](https://github.com/ArnaudBarre/eslint-plugin-react-refresh) and [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite).


Updates `react-querybuilder` from 8.22.3 to 8.22.4
- [Release notes](https://github.com/react-querybuilder/react-querybuilder/releases)
- [Changelog](https://github.com/react-querybuilder/react-querybuilder/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react-querybuilder/react-querybuilder/commits/v8.22.4/packages/react-querybuilder)

Updates `eslint-plugin-react-refresh` from 0.4.26 to 0.5.3
- [Release notes](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/releases)
- [Changelog](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/main/CHANGELOG.md)
- [Commits](ArnaudBarre/eslint-plugin-react-refresh@v0.4.26...v0.5.3)

Updates `vite` from 8.2.0 to 8.2.1
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.2.1/packages/vite)

---
updated-dependencies:
- dependency-name: react-querybuilder
  dependency-version: 8.22.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: eslint-plugin-react-refresh
  dependency-version: 0.5.3
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: vite
  dependency-version: 8.2.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 12, 2026
@alicoding
alicoding merged commit 8012bf9 into main Aug 12, 2026
16 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/frontend/npm-dependencies-8f0be22188 branch August 12, 2026 02:01
alicoding added a commit that referenced this pull request Aug 15, 2026
Was 12 direct package-function call sites in package main (Set/Get/
Delete), no interface, no injection -- unlike settings.Store, which is
already a real port every ConfigureService/CompositionService/
TriggerService consumer depends on rather than the concrete KVStore
type. Confirmed by the architecture research this session: this was the
one genuine adapter-shape gap among the three adapters checked
(settings.Store already worked as advertised; execution's DSN
parameterization, task #4, needed a one-line fix instead of this).

credential.Store mirrors settings.Store's exact shape (small interface,
a New() constructor callers depend on instead of the concrete type) --
the one difference is go-keyring itself is package-function-based with
no existing struct to satisfy the interface structurally, so a small
keyringStore{} adapter type exists solely to give those functions a
method set.

ConfigureService gained a `credentials credential.Store` field,
threaded through NewConfigureService's third parameter from main.go
(credential.New()). All 12 production call sites across
configureservice_requestauth.go, configureservice_requesttest.go, and
configureservice_builtin.go now go through c.credentials instead of the
package directly, closing the actual gap: package main's tests
(1000+ lines, wired into CI/Lefthook by task #5 this same session) were
previously the only thing exercising this code path indirectly through
keyring.MockInit() -- now the seam itself is real and independently
testable.

Verified: go vet, golangci-lint (0 issues), ls_lint, go test .
./internal/... -race -cover (root package unchanged at 57.2% coverage,
credential adapter now 100%), go build for both desktop and server
tags. All 14 test call sites across three _test.go files updated to
pass credential.New() -- still exercises the real keyring, backed by
the same keyring.MockInit() TestMain already covered the whole package
main test binary with, so no test behavior changed, only how the
dependency reaches the code under test.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
alicoding added a commit that referenced this pull request Aug 15, 2026
New capability: CompositionService.ExportWorkflow/ImportWorkflow
(compositionservice_export.go) plus a real Composition UI affordance
(Export IconButton per workflow row, an Import button + hidden file
input near New workflow) -- not backend-only, per explicit direction
that this needs to be visibly checkable in the running app, not just
git history.

Design decision the goal itself required in writing: exportedWorkflow
deliberately omits the workflow's own ID and BuiltIn flag from the wire
shape. ImportWorkflow always mints a brand-new workflow via the
existing CreateWorkflow (same validation bar as a hand-composed one --
ResolveNodeDefaults, ValidateGraph, no import-specific leniency),
matching ADR-0013's Duplicate precedent (copying an entity means a new
identity, never resurrecting the old one) -- so importing the same file
twice, or into a different Mill instance, can never silently collide
with or overwrite an existing workflow. Node/Edge IDs inside the graph
ARE preserved as-is (relative references, not global identity).

Stable/deterministic by construction, not extra bookkeeping: every
exported field is already-stored data, never regenerated on save
(confirmed by reading idgen.go directly), and Go's encoding/json
guarantees deterministic struct-field and sorted-map-key ordering. Two
exports of an unchanged workflow are therefore byte-identical -- proven
by a real test (TestExportWorkflow_IsDeterministic), not just asserted
-- which is the concrete answer to n8n's own documented git-diff-noise
problem researched earlier this session.

Two files crossed the 500-line limit adding this (CompositionView.tsx,
composition.spec.ts) -- split along real seams, not truncated:
TestRunDialog extracted to its own file (self-contained, zero shared
state with its parent beyond props, same pattern this repo already
uses); the three new e2e tests moved to composition-export-import.spec.ts
with their own workflowRow helper, matching the existing convention of
5 other spec files each keeping their own copy rather than a shared
helpers file that doesn't otherwise exist here.

Verified: 11 new Go tests (round-trip, new-ID-never-reused, two
independent imports from the same file, determinism, ID/BuiltIn
omitted from the wire shape, unknown-ID/invalid-JSON/empty-label/
invalid-graph-shape rejection, Attributes application) plus the full
existing suite, all passing with -race. Full frontend check suite
(tsc, eslint, boundaries, vitest) clean. Both e2e spec files run twice
in a row per .claude/rules/testing.md's explicit discipline for tests
creating persisted entities -- 17/17 both times, confirming cleanup
actually works, not just once. Regenerated bindings also carry two
small doc-comment-only updates trailing from task #3's Go comment
edits (configureservice.ts, models.ts) -- no functional change.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
alicoding added a commit that referenced this pull request Aug 15, 2026
…/npm-dependencies-8f0be22188

build(deps): Bump the npm-dependencies group in /frontend with 3 updates
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.

1 participant