ci(renovate): separate dev dependency prs

[roggervalf]

Port Impact Checklist

• Python – does this change need to be ported or documented in the Python library?
• Elixir – does this change need to be ported or documented in the Elixir library?
• PHP – does this change need to be ported or documented in the PHP library?
• Rust – does this change need to be ported or documented in the Rust library?
• .NET – does this change need to be ported or documented in the .NET library?

Why

1. Why is this change necessary? Commits not including port names were added in changelog. Replace [^]* with .* in the pattern. The [^] (empty negated character class matching any character including newlines) is a JavaScript-specific extension that breaks in some regex engines used by conventional-changelog. Since commit subjects are single-line, .* is correct and portable. Additionally this pr separates dev dependency upgrades by renovate in their own prs that should not trigger new releases

How

Enter the implementation details here.

Additional Notes (Optional)

Any extra info here.

[Copilot]

Pull request overview

This PR adjusts dependency-update automation and corrects generated changelog content across the main (Node.js) and port-specific documentation, so each changelog reflects only the relevant platform changes and Renovate PRs use more consistent grouping/semantic commit types.

Changes:

• Update Renovate rules to use chore for dev-dependency updates and to group dev-dependency updates separately per ecosystem (including major/non-major splits).
• Simplify the Python port’s semantic-release ignoreCommits regex used for release-notes generation.
• Fix changelog entries so Python/Elixir changelogs no longer include unrelated security/deps items, and the main changelog marks a no-Node release appropriately.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
renovate.json	Adds dev-dependency semantic commit typing and grouping rules per ecosystem (incl. major/non-major separation).
python/package.json	Updates the Python port semantic-release ignore pattern for release notes.
docs/gitbook/python/changelog.md	Removes unrelated entries and standardizes the Python dependency entry tag.
docs/gitbook/elixir/changelog.md	Removes unrelated Python/security/deps entries from the Elixir changelog.
docs/gitbook/changelog.md	Replaces a Python-only entry with “No Node.js changes.” for the Node changelog section.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated no new comments.

Suppressed comments (1)

package.json:204

• The root semantic-release commit-analyzer releaseRules contains two identical entries for the [dotnet] header matcher. This is redundant and makes the release config harder to reason about (and suggests the old (dotnet) rule was replaced but not removed). Keep a single [dotnet] rule here.

            {
              "header": "**/*\\[dotnet\\]*",
              "release": false
            },
            {
              "header": "**/*\\[dotnet\\]*",
              "release": false
            }

[github-actions]

🎉 This PR is included in version 6.0.8 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.0.4 🎉

The release is available on:

• vpy3.0.4
• GitHub release

Your semantic-release bot 📦🚀