fix(deps): update dependency stylelint to v17

[WomB0ComB0]

This PR contains the following updates:

Package	Change	Age	Confidence
stylelint (source)	^16.26.1 → ^17.0.0

---

Release Notes

stylelint/stylelint (stylelint)

v17.0.0

Compare Source

It contains 14 breaking changes, which we've detailed in the migrating to 17.0.0 guide. Additionally, it adds 3 options to the rules and fixes 9 bugs. We've also released compatible versions of our shared config, Visual Studio Code extension, Node.js Rule Tester and Jest preset.

• Removed: CommonJS Node.js API (#​8859) (@​jeddy3).
• Removed: output property in the Node.js API returned resolved object (#​8878) (@​jeddy3).
• Removed: support for Node.js less than 20.19.0 (#​8867) (@​jeddy3).
• Removed: GitHub formatter (#​8888) (@​jeddy3).
• Removed: resolveNestedSelectors option from selector-class-pattern (#​8931) (@​jeddy3).
• Removed: checkContextFunctionalPseudoClasses option from selector-max-id (#​8913) (@​jeddy3).
• Changed: default fix mode to strict (#​8889) (@​jeddy3).
• Changed: report to be consistent and predictable in how it handles the provided position arguments (#​8217) (@​romainmenke).
• Changed: selector-max-* syntax rules for standard CSS nesting and modern functional pseudo-classes (#​8913) (@​jeddy3).
• Changed: *-specificity semantic rules for standard CSS nesting (#​8913) (@​jeddy3).
• Changed: no-duplicate-selectors and selector-no-qualifying-type for standard CSS nesting (#​8913) (@​jeddy3).
• Changed: *-list rules to have consistent behaviour for vendor prefixes and case (#​8912) (@​jeddy3).
• Changed: *-no-vendor-prefix rules to have consistent behaviour for their ignore*: [] secondary options (#​8924) (@​jeddy3).
• Changed: declaration-property-max-values rule to have consistent behaviour for vendor prefixes (#​8926) (@​jeddy3).
• Added: except: ["after-block"] to custom-property-empty-line-before (#​8921) (@​kovsu).
• Added: except: ["after-block"] to declaration-empty-line-before (#​8910) (@​kovsu).
• Added: ignoreSelectors: [] to no-duplicate-selectors (#​8883) (@​kovsu).
• Fixed: Windows drive letter casing inconsistencies when matching patterns against file paths (#​8941) (@​adalinesimonian).
• Fixed: CLI help to include TypeScript config files (#​8908) (@​kovsu).
• Fixed: at-rule-descriptor-no-unknown false positives for declarations within feature-value-blocks (#​8868) (@​kovsu).
• Fixed: declaration-block-no-redundant-longhand-properties false negatives for short and long combinations (#​8892) (@​nathannewyen).
• Fixed: media-feature-name-no-unknown false positives for namespaced dollar variables and range context queries (#​8890) (@​kovsu).
• Fixed: nesting-selector-no-missing-scoping-root false positives for CSS-in-JS (#​8905) (@​kovsu).
• Fixed: no-invalid-position-declaration false negatives for embedded blocks (#​8907) (@​kovsu).
• Fixed: selector-no-qualifying-type false negatives for :is/where() (#​8940) (@​romainmenke).
• Fixed: selector-type-no-unknown false positives for MathML 4 tags (#​8874) (@​jeddy3).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
portfolio	Error		Jan 19, 2026 8:03am

[coderabbitai]

Warning

Rate limit exceeded

@WomB0ComB0 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 29 minutes and 17 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4ab0125 and da3a274.

📒 Files selected for processing (1)

• package.json

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @WomB0ComB0, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the stylelint dependency to its major version 17.0.0. This upgrade is necessary to leverage the latest features and bug fixes, but it also introduces several breaking changes that may require adjustments to the project's linting configuration or codebase. The primary impact is ensuring compatibility with the new stylelint API and rule behaviors.

Highlights

• Dependency Update: Updates the stylelint package from version 16.x to 17.x. This is a major version upgrade.
• Breaking Changes: The update to stylelint v17 introduces 14 breaking changes, including the removal of CommonJS Node.js API support, dropping Node.js versions less than 20.19.0, and changes to various rule behaviors. A migration guide is available in the stylelint release notes.
• New Features and Fixes: The new stylelint version adds 3 new rule options and fixes 9 bugs, improving the linter's functionality and stability.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR updates stylelint to a new major version (v17). This is a significant update with several breaking changes as noted in the release notes. While updating dependencies is good practice, this major version bump requires careful consideration. Specifically, stylelint-config-standard-scss might not be compatible with stylelint v17, which could break your linting setup. Please see my comment on package.json. Also, be aware that stylelint v17 requires Node.js >= 20.19.0 and changes the default behavior of the --fix flag. It's recommended to run the lint script locally to ensure everything works as expected after this update.

[gemini-code-assist]

Updating stylelint to v17 is a major change that likely introduces breaking changes for its ecosystem. The stylelint-config-standard-scss package is likely not compatible with stylelint v17.

Most stylelint plugins and shared configs declare stylelint as a peer dependency with a specific version range. A major version bump of stylelint usually requires corresponding major version bumps of its plugins and configs.

Installing stylelint@17 without updating stylelint-config-standard-scss will likely cause peer dependency conflicts and may break your linting command.

Recommendation:
Please verify that stylelint-config-standard-scss has a version compatible with stylelint@17 and update it in this PR as well. If a compatible version is not yet available, it would be best to postpone this stylelint update to avoid breaking the linting process.