[PR #1397] [MERGED] fix: let the CVE timeline rules pass stylelint so PR CI runs green again #1362

New issue

Closed

opened 2026-10-18 14:19:08 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:19:08 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/1397
Author: @silentoplayz
Created: 9/18/2026
Status: ✅ Merged
Merged: 9/18/2026
Merged by: @Classic298

Base: main ← Head: docs/stylelint-cve-rules

📝 Commits (1)

30e0c2f fix: let the CVE timeline rules pass stylelint so PR CI runs green again

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

📝 src/css/custom.css (+3 -0)

📄 Description

Summary

Every pull request against this repository has failed the CI workflow since the CVE timeline styles landed in src/css/custom.css. The Run stylelint step reports three no-descending-specificity errors on main itself (the table tr:has(.cve-rejected) pair and .cve-resolved .theme-admonition), and nothing on main runs stylelint because the workflow is triggered by pull_request only, so the failure shows up on other people's PRs and never on the commit that caused it.

This adds a stylelint-disable-next-line no-descending-specificity comment above each of the three rules, which is how the rest of the file already handles the same rule for the table styles. No selector or declaration changes, so the rendered site is unchanged. npm run stylelint passes with this commit.

None. The failing runs are visible on #1387, #1388, #1390, #1395 and #1396.

Checklist

I have reviewed the relevant documentation and matched the existing style.
This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility.
I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories.

Notes for reviewers

Reproduced locally with the repository's own stylelint on main's custom.css: three errors before, none after. Once this merges, the open PRs go green on their next run without changes of their own.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/docs/pull/1397 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 9/18/2026 **Status:** ✅ Merged **Merged:** 9/18/2026 **Merged by:** [@Classic298](https://github.com/Classic298) **Base:** `main` ← **Head:** `docs/stylelint-cve-rules` --- ### 📝 Commits (1) - [`30e0c2f`](https://github.com/open-webui/docs/commit/30e0c2f0b118b91155f73fb8aeb1d8897269823c) fix: let the CVE timeline rules pass stylelint so PR CI runs green again ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/css/custom.css` (+3 -0) </details> ### 📄 Description ## Summary Every pull request against this repository has failed the `CI` workflow since the CVE timeline styles landed in `src/css/custom.css`. The `Run stylelint` step reports three `no-descending-specificity` errors on `main` itself (the `table tr:has(.cve-rejected)` pair and `.cve-resolved .theme-admonition`), and nothing on `main` runs stylelint because the workflow is triggered by `pull_request` only, so the failure shows up on other people's PRs and never on the commit that caused it. This adds a `stylelint-disable-next-line no-descending-specificity` comment above each of the three rules, which is how the rest of the file already handles the same rule for the table styles. No selector or declaration changes, so the rendered site is unchanged. `npm run stylelint` passes with this commit. ## Related issue or discussion None. The failing runs are visible on #1387, #1388, #1390, #1395 and #1396. ## Checklist - [x] I have reviewed the relevant documentation and matched the existing style. - [x] This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility. - [x] I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories. ## Notes for reviewers Reproduced locally with the repository's own stylelint on `main`'s `custom.css`: three errors before, none after. Once this merges, the open PRs go green on their next run without changes of their own. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:19:08 +00:00