chore(ZMSKVR): Bump eslint to 10.0.1 and bump container environment to node 22#2007
chore(ZMSKVR): Bump eslint to 10.0.1 and bump container environment to node 22#2007ThomasAFink wants to merge 4 commits intonextfrom
Conversation
📝 WalkthroughWalkthroughBumped Node.js version from 18 → 22 in dev container and DDEV config; added Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
zmscalldisplay/package.json (1)
40-40: Optional: prefer~over^for ESLint version pin.ESLint recommends using the tilde (
~) inpackage.json, e.g."eslint": "~3.1.0", to guarantee the results of your builds. A caret allows minor bumps which, per ESLint's policy, may report additional linting errors.♻️ Proposed change
- "eslint": "^10.0.1", + "eslint": "~10.0.1",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@zmscalldisplay/package.json` at line 40, Update the ESLint dependency specifier from a caret to a tilde in package.json by changing the "eslint" entry from "^10.0.1" to "~10.0.1" so minor version bumps are prevented; after editing the "eslint" line, run your package manager (npm/yarn/pnpm) to regenerate the lockfile (package-lock.json or yarn.lock) and ensure CI builds pick up the updated pinned version..devcontainer/Containerfile (1)
51-52:setup_22.xinstall script is deprecated by NodeSource.NodeSource states: "Installation Scripts: The installation scripts
setup_XX.xare no longer supported and are not needed anymore, as the installation process is straightforward for any RPM and DEB distro. It's essential to clarify that 'no longer supported' doesn't mean the scripts are 'unavailable' or 'not accessible.' Instead, these scripts are now deprecated."When run, the script emits a `SCRIPT DEPRECATION WARNING: This script, located at https://deb.nodesource.com/setup_X, used to install Node.js is deprecated now and will eventually be made inactive. This will pollute build logs and may eventually break the container build.
Consider migrating to the official NodeSource DEB method as documented at https://github.com/nodesource/distributions.
♻️ Proposed migration to the recommended NodeSource DEB setup
-RUN curl -fsSL https://deb.nodesource.com/setup_22.x | bash - \ - && apt-get install -y nodejs +RUN apt-get update && apt-get install -y ca-certificates gnupg \ + && curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key \ + | gpg --dearmor -o /usr/share/keyrings/nodesource.gpg \ + && echo "deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main" \ + > /etc/apt/sources.list.d/nodesource.list \ + && apt-get update && apt-get install -y nodejsVerify the exact recommended commands against the latest NodeSource distributions README before applying.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.devcontainer/Containerfile around lines 51 - 52, Replace the deprecated "RUN curl -fsSL https://deb.nodesource.com/setup_22.x | bash - ..." invocation: instead add the official NodeSource DEB repository setup sequence (install any needed prerequisites like ca-certificates/gnupg/lsb-release, import NodeSource GPG key into /usr/share/keyrings or via apt-key, create the nodesource list file with the appropriate "deb [signed-by=...] https://deb.nodesource.com node_22.x <distro-codename> main", run apt-get update) and then apt-get install -y nodejs; reference the existing RUN line that uses setup_22.x and replace it with these repository setup steps, and verify exact commands against the NodeSource distributions README before committing.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.ddev/config.yaml:
- Around line 89-90: Update the stale comment for the nodejs_version example so
it includes Node 22; locate the commented example for nodejs_version (the
commented line starting with "nodejs_version") and modify its example list from
"14, 16, 18, 20" to include "22" (e.g., "14, 16, 18, 20, 22") so the comment
matches the currently-configured value.
In `@zmscalldisplay/package.json`:
- Around line 40-41: The package.json currently pairs "eslint": "^10.0.1" with
"eslint-plugin-import": "^2.24.2" which is incompatible with ESLint 10; update
package.json to either (A) upgrade "eslint-plugin-import" to a v3.x release that
lists ESLint 10 in its peerDependencies (replace the "eslint-plugin-import"
version string with a v3.x caret-release) and run npm/yarn install and test
linting, or (B) revert "eslint" to a ^9.x version (change the "eslint" entry to
a v9 caret) if you must keep the v2 plugin; also verify the "lint" script
("lint": "eslint js/") works with ESLint 10’s config lookup behavior or
co-locate eslint.config.* with source files.
---
Duplicate comments:
In `@zmsadmin/package.json`:
- Around line 35-37: The package.json pins for "eslint", "eslint-plugin-import",
and "eslint-plugin-react" may be incompatible with ESLint 10's flat config API;
verify the compatibility by checking each plugin's peerDependencies (use
npm/registry or curl to inspect eslint-plugin-react and eslint-plugin-import
metadata) and run a quick lint pass with ESLint 10 against this repo (zmsadmin)
to surface breaking changes; if a plugin version does not declare support for
ESLint 10, upgrade the dependency to a published version that lists eslint@^10
in peerDependencies or add a compatible replacement (or an overrides/resolutions
entry) and update any config/usage in your flat config to match the plugin's
supported API (target symbols: the "eslint", "eslint-plugin-import", and
"eslint-plugin-react" entries in zmsadmin/package.json and any react-related
ESLint config files).
In `@zmsstatistic/package.json`:
- Around line 34-35: The eslint-plugin-import dependency in package.json
("eslint-plugin-import": "^2.20.1") is very old and may be incompatible with the
declared eslint ("eslint": "^10.0.1"); verify compatibility and either upgrade
the plugin to a version that supports ESLint 10 or pin ESLint to a version the
plugin supports. Inspect the package.json entries "eslint" and
"eslint-plugin-import", run the provided ripgrep check (rg --type=js
'\/\*\s*eslint-env' zmsstatistic/js/) to find any file-level eslint-env pragmas
that could affect rules, and then update package.json accordingly and re-run
lint to confirm no rule/runtime errors.
In `@zmsticketprinter/package.json`:
- Line 40: The package.json upgrade to "eslint": "^10.0.1" can introduce the
same ESLint-10 config-lookup and /* eslint-env */ inline comment issues noted
for zmscalldisplay; either pin zmsticketprinter's eslint to a 9.x range or
update this package's lint configuration to explicitly declare environments and
root behavior (add an eslintConfig block with "env" entries and "root": true or
equivalent new ESLint 10 settings) and remove/replace any /* eslint-env */ file
comments. Locate the package.json entry ("eslint": "^10.0.1") and run the
supplied rg command (rg --type=js '\/\*\s*eslint-env' zmsticketprinter/js/) to
find offending inline eslint-env comments, then remove them and ensure
environments are defined in package.json's eslintConfig or shared config so
ESLint 10 behaves correctly.
---
Nitpick comments:
In @.devcontainer/Containerfile:
- Around line 51-52: Replace the deprecated "RUN curl -fsSL
https://deb.nodesource.com/setup_22.x | bash - ..." invocation: instead add the
official NodeSource DEB repository setup sequence (install any needed
prerequisites like ca-certificates/gnupg/lsb-release, import NodeSource GPG key
into /usr/share/keyrings or via apt-key, create the nodesource list file with
the appropriate "deb [signed-by=...] https://deb.nodesource.com node_22.x
<distro-codename> main", run apt-get update) and then apt-get install -y nodejs;
reference the existing RUN line that uses setup_22.x and replace it with these
repository setup steps, and verify exact commands against the NodeSource
distributions README before committing.
In `@zmscalldisplay/package.json`:
- Line 40: Update the ESLint dependency specifier from a caret to a tilde in
package.json by changing the "eslint" entry from "^10.0.1" to "~10.0.1" so minor
version bumps are prevented; after editing the "eslint" line, run your package
manager (npm/yarn/pnpm) to regenerate the lockfile (package-lock.json or
yarn.lock) and ensure CI builds pick up the updated pinned version.
| "eslint": "^10.0.1", | ||
| "eslint-plugin-import": "^2.24.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
echo "=== Checking eslint-plugin-import latest version and peer dependencies ==="
curl -s https://registry.npmjs.org/eslint-plugin-import/latest 2>/dev/null | jq '{version: .version, peerDependencies: .peerDependencies}' || echo "Failed to fetch from registry"
echo ""
echo "=== Searching for eslint-env comments in zmscalldisplay/js/ ==="
cd zmscalldisplay && rg --type=js '/\*\s*eslint-env' js/ || echo "No eslint-env comments found"Repository: it-at-m/eappointment
Length of output: 352
🌐 Web query:
ESLint 10.0.0 breaking changes config file lookup behavior
💡 Result:
In ESLint 10.0.0, the flat config lookup behavior is a breaking change:
- Config lookup now starts from each linted file’s directory and searches upward for
eslint.config.*(instead of relying on the old cwd-based lookup many setups assumed). This is now the default. [1] - The feature flag
v10_config_lookup_from_filewas removed; if you still pass it (CLI--flag ...,ESLINT_FLAGS, or APIflags), ESLint 10 will error. [1] - If you need the prior “single config from where you ran ESLint” behavior, you must pin the config explicitly (for example
--config path/to/eslint.config.js). [1]
Sources:
[1] ESLint “Migrate to v10.x” – “New configuration file lookup algorithm”. (eslint.org)
Citations:
🌐 Web query:
eslint-plugin-import compatibility ESLint 10
💡 Result:
As of eslint-plugin-import v2.32.0 (Jun 20, 2025), it is not officially compatible with ESLint 10 because its peerDependencies only allow ESLint ^2 … ^9 (no ^10). [1]
What this means in practice with ESLint 10 (released Feb 6, 2026):
- Your package manager will likely show/throw a peer dependency conflict when you try to install ESLint 10 alongside eslint-plugin-import. [2][1]
- It may still run at runtime, but that’s unsupported until the plugin updates its peer range. One ESLint-10 upgrade report noted they had to force-install eslint-plugin-import due to peer dep conflicts, but “verified functionality.” [4]
Extra ESLint 10 gotcha: ESLint 10 removes support for the old/legacy config format, so you’ll need flat config (or compat tooling) regardless of plugin choice. [3]
Update eslint-plugin-import to support ESLint 10, or revert ESLint to v9.
ESLint v10.0.0 includes a breaking change in config file lookup behavior: the configuration is now located starting from each linted file's directory (rather than from the current working directory). This may affect the "lint": "eslint js/" script unless eslint.config.* is co-located with source files.
More critically, eslint-plugin-import v2.x (including the currently installed v2.24.2) does not officially support ESLint 10. The latest v2 release (v2.32.0) explicitly limits peer dependencies to eslint: ^2 || ... || ^9 with no support for ^10. To proceed with ESLint 10, either update eslint-plugin-import to a v3.x release that supports ESLint 10, or revert ESLint to v9.x.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@zmscalldisplay/package.json` around lines 40 - 41, The package.json currently
pairs "eslint": "^10.0.1" with "eslint-plugin-import": "^2.24.2" which is
incompatible with ESLint 10; update package.json to either (A) upgrade
"eslint-plugin-import" to a v3.x release that lists ESLint 10 in its
peerDependencies (replace the "eslint-plugin-import" version string with a v3.x
caret-release) and run npm/yarn install and test linting, or (B) revert "eslint"
to a ^9.x version (change the "eslint" entry to a v9 caret) if you must keep the
v2 plugin; also verify the "lint" script ("lint": "eslint js/") works with
ESLint 10’s config lookup behavior or co-locate eslint.config.* with source
files.
There was a problem hiding this comment.
Is eslint-plugin-import used at all in zmscalldisplay @coderabbitai?
There was a problem hiding this comment.
@coderabbitai what about zmsadmin zmsstatistic and zmsticketprinter too?
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
echo "=== Looking for ESLint configuration files in zmscalldisplay ==="
fd -t f 'eslint\.config\.(js|mjs|cjs)$|\.eslintrc\.(js|json|yml|yaml)$|\.eslintrc$' zmscalldisplay/
echo ""
echo "=== Checking if eslint-plugin-import is referenced in any config files ==="
rg -n "eslint-plugin-import|plugin.*import" zmscalldisplay/ -g '*.{js,json,yml,yaml,mjs,cjs}' -g 'eslint*' || echo "No references found"
echo ""
echo "=== Checking for import/* rule usage in JS files ==="
rg -n "eslint.*import/" zmscalldisplay/js/ || echo "No import/* rule comments found"
echo ""
echo "=== List all files in zmscalldisplay for context ==="
fd -t f . zmscalldisplay/ --max-depth 2
Length of output: 1593
🏁 Script executed:
#!/bin/bash
echo "=== Checking if JS files use import statements ==="
echo ""
echo "--- zmscalldisplay/js/index.js ---"
head -30 zmscalldisplay/js/index.js
echo ""
echo "--- zmscalldisplay/js/settings.js ---"
head -30 zmscalldisplay/js/settings.js
echo ""
echo "=== Searching for import statements in all JS files ==="
rg -n "^import\s+.*from\s+" zmscalldisplay/js/ || echo "No ES6 import statements found"
Length of output: 2746
🏁 Script executed:
#!/bin/bash
echo "=== Searching for ESLint config files in all modules ==="
fd -t f 'eslint\.config\.(js|mjs|cjs)$|\.eslintrc\.(js|json|yml|yaml)$|\.eslintrc$' zmsadmin/ zmsstatistic/ zmsticketprinter/ zmscitizenview/ || echo "No ESLint config files found in any module"
echo ""
echo "=== Checking package.json files for eslint-plugin-import in all modules ==="
rg -n "eslint-plugin-import" zmsadmin/package.json zmsstatistic/package.json zmsticketprinter/package.json zmscitizenview/package.json || echo "Not found in other modules"
Length of output: 297
🏁 Script executed:
#!/bin/bash
echo "=== Contents of zmscitizenview/eslint.config.js ==="
cat zmscitizenview/eslint.config.js
echo ""
echo "=== Double-check all module directories for ESLint configs ==="
fd -t f 'eslint\.config\.(js|mjs|cjs)$|\.eslintrc' zmsadmin/ zmsstatistic/ zmsticketprinter/ zmscalldisplay/ || echo "None found"
Length of output: 965
@ThomasAFink No, eslint-plugin-import is not being used in zmscalldisplay.
My investigation found:
- ❌ No ESLint configuration file exists in zmscalldisplay (no
.eslintrcoreslint.config.js) - ✅ The JS files do use ES6 imports extensively
- 📦 The plugin is listed in
devDependenciesbut cannot be active without a config file
Recommendation: You can safely remove eslint-plugin-import from zmscalldisplay's package.json since it's unused. Without an ESLint config, the plugin serves no purpose, and my earlier compatibility warning about ESLint 10 doesn't apply here.
The same pattern appears in other modules (zmsadmin, zmsstatistic, zmsticketprinter) - they also lack ESLint configs despite having the plugin in devDependencies. Only zmscitizenview has an eslint.config.js, though it doesn't use the import plugin either.
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
echo "=== Checking zmsadmin for eslint-plugin-import ==="
echo "--- package.json ---"
if [ -f "zmsadmin/package.json" ]; then
cat zmsadmin/package.json | jq '.devDependencies["eslint-plugin-import"], .dependencies["eslint-plugin-import"]' 2>/dev/null || echo "Not found in dependencies"
else
echo "zmsadmin/package.json not found"
fi
echo ""
echo "--- ESLint config files ---"
fd -t f 'eslint\.config\.|\.eslintrc' zmsadmin/ 2>/dev/null || echo "No ESLint config files found"
echo ""
echo "--- Usage in source code ---"
rg -i 'eslint-plugin-import|plugin:import' zmsadmin/ --max-count=5 2>/dev/null || echo "No references found"
echo ""
echo "=== Checking zmsstatistic for eslint-plugin-import ==="
echo "--- package.json ---"
if [ -f "zmsstatistic/package.json" ]; then
cat zmsstatistic/package.json | jq '.devDependencies["eslint-plugin-import"], .dependencies["eslint-plugin-import"]' 2>/dev/null || echo "Not found in dependencies"
else
echo "zmsstatistic/package.json not found"
fi
echo ""
echo "--- ESLint config files ---"
fd -t f 'eslint\.config\.|\.eslintrc' zmsstatistic/ 2>/dev/null || echo "No ESLint config files found"
echo ""
echo "--- Usage in source code ---"
rg -i 'eslint-plugin-import|plugin:import' zmsstatistic/ --max-count=5 2>/dev/null || echo "No references found"
echo ""
echo "=== Checking zmsticketprinter for eslint-plugin-import ==="
echo "--- package.json ---"
if [ -f "zmsticketprinter/package.json" ]; then
cat zmsticketprinter/package.json | jq '.devDependencies["eslint-plugin-import"], .dependencies["eslint-plugin-import"]' 2>/dev/null || echo "Not found in dependencies"
else
echo "zmsticketprinter/package.json not found"
fi
echo ""
echo "--- ESLint config files ---"
fd -t f 'eslint\.config\.|\.eslintrc' zmsticketprinter/ 2>/dev/null || echo "No ESLint config files found"
echo ""
echo "--- Usage in source code ---"
rg -i 'eslint-plugin-import|plugin:import' zmsticketprinter/ --max-count=5 2>/dev/null || echo "No references found"
Length of output: 1514
🏁 Script executed:
#!/bin/bash
echo "=== Checking for root-level ESLint config files ==="
fd -t f 'eslint\.config\.|\.eslintrc' -d 2 --exclude node_modules --exclude .git 2>/dev/null | head -20
echo ""
echo "=== Checking if eslint-plugin-import is configured in any ESLint configs ==="
rg -i 'plugin.*import|import/' --type-add 'config:*.{js,cjs,mjs,json}' --type config -g 'eslint*' --max-count=3 2>/dev/null || echo "No plugin configuration found"
echo ""
echo "=== Checking zmsadmin for actual plugin usage in ESLint config ==="
if [ -f "zmsadmin/eslint.config.js" ] || [ -f "zmsadmin/eslint.config.mjs" ] || [ -f "zmsadmin/eslint.config.cjs" ]; then
cat zmsadmin/eslint.config.* 2>/dev/null | head -50
elif [ -f "zmsadmin/.eslintrc.js" ] || [ -f "zmsadmin/.eslintrc.json" ] || [ -f "zmsadmin/.eslintrc" ]; then
cat zmsadmin/.eslintrc* 2>/dev/null | head -50
else
echo "No ESLint config file found in zmsadmin/"
fi
echo ""
echo "=== Checking zmsstatistic for actual plugin usage in ESLint config ==="
if [ -f "zmsstatistic/eslint.config.js" ] || [ -f "zmsstatistic/eslint.config.mjs" ] || [ -f "zmsstatistic/eslint.config.cjs" ]; then
cat zmsstatistic/eslint.config.* 2>/dev/null | head -50
elif [ -f "zmsstatistic/.eslintrc.js" ] || [ -f "zmsstatistic/.eslintrc.json" ] || [ -f "zmsstatistic/.eslintrc" ]; then
cat zmsstatistic/.eslintrc* 2>/dev/null | head -50
else
echo "No ESLint config file found in zmsstatistic/"
fi
echo ""
echo "=== Checking zmscalldisplay for actual plugin usage in ESLint config ==="
if [ -f "zmscalldisplay/eslint.config.js" ] || [ -f "zmscalldisplay/eslint.config.mjs" ] || [ -f "zmscalldisplay/eslint.config.cjs" ]; then
cat zmscalldisplay/eslint.config.* 2>/dev/null | head -50
elif [ -f "zmscalldisplay/.eslintrc.js" ] || [ -f "zmscalldisplay/.eslintrc.json" ] || [ -f "zmscalldisplay/.eslintrc" ]; then
cat zmscalldisplay/.eslintrc* 2>/dev/null | head -50
else
echo "No ESLint config file found in zmscalldisplay/"
fi
Length of output: 2716
@ThomasAFink Yes, zmsadmin and zmsstatistic have the same compatibility issue:
✅ Modules with actual eslint-plugin-import usage:
- zmsadmin: Has
eslint-plugin-import ^2.24.2and actively uses it in.eslintrc.jsonwith"plugin:import/warnings"and"plugin:import/errors"extends - zmsstatistic: Has
eslint-plugin-import ^2.20.1and actively uses it in.eslintrc.jswith"plugin:import/warnings"and"plugin:import/errors"extends
Both will encounter peer dependency conflicts with ESLint 10.
❌ Modules without actual usage:
- zmscalldisplay: Has the plugin installed (
^2.24.2) but doesn't use it in.eslintrc.js(only extends"eslint:recommended") — the dependency can be safely removed - zmsticketprinter: Doesn't have the plugin installed at all — no issue
Recommendation: For zmsadmin and zmsstatistic, you'll need to either upgrade eslint-plugin-import to a v3.x release that supports ESLint 10, or revert ESLint to v9.x. For zmscalldisplay, you can remove the unused eslint-plugin-import dependency.
There was a problem hiding this comment.
@ThomasAFink Yes, you're absolutely right that ESLint 9.39 works fine! My concern is specifically about the upgrade to ESLint 10.
There's an active issue (#3227) showing that eslint-plugin-import encounters runtime errors with ESLint 10, specifically a TypeError: Cannot use 'in' operator to search for 'sourceType' in undefined. This isn't just a peer dependency warning—it's an actual breaking error that occurs when the plugin runs.
Since zmsadmin and zmsstatistic actively use eslint-plugin-import in their ESLint configs, they would encounter this error after upgrading to ESLint 10.
Your options:
-
Test it: Try running
npm run lintin zmsadmin and zmsstatistic after the ESLint 10 upgrade. If linting still works without errors, you're good to go. -
Wait for a fix: Monitor the issue for a resolution before merging.
-
Stay on ESLint 9: Keep using
"eslint": "^9.39.1"until eslint-plugin-import officially supports v10. -
Remove the plugin: If you confirm it's not actually needed (like in zmscalldisplay), remove it from the affected packages.
Would you like me to check if the lint scripts actually run successfully in the CI, or test whether the plugin is genuinely required in zmsadmin and zmsstatistic?
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain
🏁 Script executed: Length of output: 1569 🏁 Script executed: Length of output: 1732 🏁 Script executed: Length of output: 943 🏁 Script executed: Length of output: 312
The error occurs because npm expects SolutionYou need to add Prettier to the Option 1: Using npm (recommended) cd zmscitizenview
npm install --save-dev prettier@3.8.1Option 2: Manual edit
"prettier": "^3.8.1"
cd zmscitizenview
npm installAfter either option, commit both |
|
Merge when import-js/eslint-plugin-import#3227 is resolved. |
There was a problem hiding this comment.
♻️ Duplicate comments (1)
.ddev/config.yaml (1)
89-90: Comment already addressed.The example comment at line 89 and the version list at line 90 now correctly reflect Node.js 22.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.ddev/config.yaml around lines 89 - 90, The duplicate review marker/comment has already been addressed but remains in the file; remove the redundant duplicate comment text and any leftover "[duplicate_comment]" annotation so the commented example lines for nodejs_version ("# nodejs_version: \"22\"" and the following explanatory line) remain clean and not duplicated, ensuring the only references are the commented example and the version list entries.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In @.ddev/config.yaml:
- Around line 89-90: The duplicate review marker/comment has already been
addressed but remains in the file; remove the redundant duplicate comment text
and any leftover "[duplicate_comment]" annotation so the commented example lines
for nodejs_version ("# nodejs_version: \"22\"" and the following explanatory
line) remain clean and not duplicated, ensuring the only references are the
commented example and the version list entries.
1 participant
Pull Request Checklist (Feature Branch to
next):nextBranch in meinen Feature-Branch gemergt.Summary by CodeRabbit