chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates - #276
Merged
rubenvdlinde merged 1 commit intoAug 30, 2026
Merged
Conversation
dependabot
Bot
added
dependencies
Contributor
|
@dependabot rebase |
…dates Bumps the npm_and_yarn group with 2 updates in the / directory: [fast-xml-parser](https://github.com/NaturalIntelligence/fast-xml-parser) and [js-yaml](https://github.com/nodeca/js-yaml). Updates `fast-xml-parser` from 4.5.7 to 5.11.1 - [Release notes](https://github.com/NaturalIntelligence/fast-xml-parser/releases) - [Changelog](https://github.com/NaturalIntelligence/fast-xml-parser/blob/master/CHANGELOG.md) - [Commits](NaturalIntelligence/fast-xml-parser@v4.5.7...v5.11.1) Updates `js-yaml` from 4.1.1 to 4.3.2 - [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.2/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.1...4.3.2) --- updated-dependencies: - dependency-name: fast-xml-parser dependency-version: 5.11.1 dependency-type: indirect - dependency-name: js-yaml dependency-version: 4.3.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/npm_and_yarn-20534e3d56
branch
from
August 30, 2026 16:54
6b13878 to
fafc553
Compare
rubenvdlinde
deleted the
dependabot/npm_and_yarn/npm_and_yarn-20534e3d56
branch
August 30, 2026 17:56
rubenvdlinde
added a commit
that referenced
this pull request
Aug 31, 2026
… at all (#304) * fix(eslint): migrate to flat config, the fleet's standard eslint could not run here at all once its version moved: Oops! Something went wrong! :( ESLint: 10.9.1 ESLint couldn't find an eslint.config.* file. versioniq was the LAST app in the fleet still on .eslintrc.cjs; every other one already ships eslint.config.mjs. That was invisible while the lockfile held eslint 8.57.1, and surfaced the moment a Dependabot group bump pulled eslint 10 -- which requires flat config. development branch eslint 8.57.1 .eslintrc.cjs works dependabot #276 eslint 10.9.1 crashes before linting a file This takes hermiq's eslint.config.mjs, which documents itself as the fleet's canonical shape ('copy it verbatim; only the last two blocks should differ'), and keeps versioniq's own rules in those two blocks with their original rationales. The jsdoc rules from .eslintrc.cjs are NOT carried over: the canonical config already scopes them and already declares the tag that gate-16 needs. Re-declaring them unscoped aborts the whole run -- which it did, once, before this was corrected. Fixing the config surfaced 247 findings it had been unable to report. 194 were auto-fixable. Of the rest: 24x import-extensions/extensions relative imports now carry .ts, checked against the file on disk rather than appended blindly 4x no-use-before-define two refs declared 90 lines below their first use, moved above it Verified: eslint exits 0 (113 warnings, 0 errors), stylelint exits 0, webpack build compiles, vitest 11 files / 58 tests pass. * fix(stylelint): give stylelint a configuration at all Aligning the lockfile for the eslint migration moved stylelint 16 -> 17, and 17 refused to start: ConfigurationError: No rules found within configuration. Have you provided a "rules" property? The cause was not the upgrade. This app declared `@nextcloud/stylelint-config` as a devDependency and then never extended it -- no config file of any kind, and no `stylelint` key in package.json. stylelint 16 tolerated that silently. A declared linter with no rules is not a lenient linter, it is an absent one: the package was installed on every CI run and judged nothing. The 16 -> 17 move did not break stylelint here, it revealed that stylelint had never been running. It now has a config pointing at the package it already depended on, written as `export default` rather than `module.exports` because this package is `"type": "module"` and a `.js` config file is therefore an ES module -- CommonJS there throws `ReferenceError: module is not defined in ES module scope`. With stylelint finally running it reported 70 findings; 59 were auto-fixable and the remainder were logical-property warnings (padding-left -> padding-inline-start), which are warnings and do not fail the run. The v3 stylelint stack is now declared explicitly rather than inherited: stylelint ^17.14.1, @nextcloud/stylelint-config ^3.2.2, stylelint-config-recommended-scss ^17.0.1, stylelint-config-recommended-vue ^1.6.1 and stylelint-config-html ^1.1.0 -- the same set shillinq and zaakafhandelapp run green. Note on the previous commit: its message lost the word `spec` from one sentence. Backticks in a double-quoted `-m` string were expanded by the shell before git saw them. It should read "already declares the `spec` tag that gate-16 requires". Left uncorrected because amending would need a force-push onto a shared branch. Verified: eslint exits 0 (113 warnings, 0 errors), stylelint exits 0, webpack build compiles, vitest 11 files / 58 tests pass. --------- Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps the npm_and_yarn group with 2 updates in the / directory: fast-xml-parser and js-yaml.
Updates
fast-xml-parserfrom 4.5.7 to 5.11.1Release notes
Sourced from fast-xml-parser's releases.
... (truncated)
Changelog
Sourced from fast-xml-parser's changelog.
... (truncated)
Commits
36175505.11.16021128update for release6ddcb65remove regex from validator7d60815docs: fix two 404 documentation links (#862)4e3857bBump actions/setup-node from 6.4.0 to 7.0.0 (#854)fcc62fbBump zizmorcore/zizmor-action from 0.5.7 to 0.6.1 (#856)23a9019Bump actions/checkout from 7.0.0 to 7.0.1 (#858)f3c69ae5.11.0fdbd072update for releasec5fcb5bupdate lock filesUpdates
js-yamlfrom 4.1.1 to 4.3.2Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
79ca68d4.3.2 releasedd90b661Backport merge limits from v5.4.186e91b84.3.1 releasedc3cc4b0Backport quadratic complexity fix for !!omap33d05b54.3.0 released663bfabDrop demo publish, to not override new v5 one.1cb8c7bAdd v4-legacy tag for publish02f27afRestore umd builds back to es58be84edFix es5 compatibility59423c6ReplacemaxMergeSeqLengthoption withmaxTotalMergeKeys(more robust). Ba...