Add new themes introduced in @node-red-contrib-themes/theme-collection v4.1

[bonanitech]

Proposed Changes

Node-RED Contrib Theme Collection version 4.1 introduced new themes:

• night-owl
• noctis-azureus
• noctis-bordo
• noctis-minimus
• noctis-obscuro
• noctis-sereno
• noctis-uva
• noctis-viola
• railscasts-extended
• selenized-dark
• selenized-light
• zendesk-garden

This PR adds them to the add-on config.

Related Issues

(Github link to related issues or pull requests)

Summary by CodeRabbit

• New Features
  • Expanded the selection of available themes for Node-RED with several new options, including additional "noctis" variants, "night-owl," "railscasts-extended," "selenized-dark," "selenized-light," and "zendesk-garden."
• Documentation
  • Updated documentation to reflect the newly added theme options in the configuration.

[coderabbitai]

Walkthrough

The documentation and configuration schema for the Node-RED Home Assistant add-on were updated to expand the list of available UI themes. Multiple new themes were added to both the documentation and the configuration schema, increasing the customization options for users. No code or functional changes were made.

Changes

File(s)	Summary of Changes
node-red/DOCS.md	Updated documentation to list new available UI themes under the theme configuration section.
node-red/config.yaml	Expanded the allowed values for the theme option in the configuration schema to include the new themes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In Node-RED’s garden, new colors bloom bright,
Noctis and night-owl now join the light.
Railscasts extended, selenized too,
Zendesk-garden brings a fresh view.
With themes aplenty, the palette’s complete—
A rabbit’s delight, so cheerful and neat!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[bonanitech]

Marking as "ready for review". The release of Node-RED v4.1 seems imminent.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

node-red/config.yaml (1)

52-52: List grows—consider maintainability tooling

The ever-expanding regex list is becoming unwieldy and error-prone to edit manually. A small helper (e.g. a CI job that fetches the latest theme names from @node-red-contrib-themes/theme-collection and regenerates this line) would prevent future typos/omissions and keep schema & docs in sync automatically.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4333573 and 450fa60.

📒 Files selected for processing (2)

• node-red/DOCS.md (1 hunks)
• node-red/config.yaml (1 hunks)

🔇 Additional comments (1)

node-red/DOCS.md (1)

126-150: Docs in sync—looks good

New theme bullets match the schema exactly and remain alphabetically ordered.

[frenck]

Nice! Thanks, @bonanitech 👍

../Frenck