[mtrezza]

Closes #919

Changes

• 14.1.1: Updated dependency get-stream to v9 (fix(deps): update dependency get-stream to v9 semantic-release/release-notes-generator#613). In the published package this removes the get-stream and into-stream dependencies entirely: generateNotes now renders with writeChangelogString(commits, context, options) from conventional-changelog-writer instead of piping the commits through into-stream into writeChangelogStream and collecting the output with get-stream. Both writer functions use the same internal generator, commit transform and template renderer. 14.1.1 was published with npm provenance from semantic-release/release-notes-generator@9728887.

Breaking Changes

None

Code Changes Required

None — the upgrade is a drop-in replacement.

Lock file

• node_modules/@semantic-release/release-notes-generator: 14.1.0 → 14.1.1 (npm 10 also records "license": "MIT" in the entry)
• Removed, no longer needed by any package: node_modules/from2 2.3.0, node_modules/get-stream 7.0.1, node_modules/into-stream 7.0.0, node_modules/p-is-promise 3.0.0
• No other entries change. conventional-changelog-writer 8.0.0, conventional-commits-parser 6.0.0, conventional-commits-filter 5.0.0, conventional-changelog-angular 8.0.0 and handlebars 4.7.10 stay as they are. semantic-release 25.0.9 requires ^14.1.0 and keeps using the single hoisted copy.
• The lock was generated on the current master (1cce959). The lock in refactor: Bump @semantic-release/release-notes-generator from 14.1.0 to 14.1.1 #919 was generated on b5bf542 (refactor: Bump parse-server from 9.9.0 to 9.10.0 #935), before 11 later merges. Its own change matches this one, but the rest of its lock content is outdated (for example root version 3.0.0, semantic-release 25.0.3, handlebars 4.7.9).

Release notes verification

The release notes are rendered with custom templates (.releaserc/*.hbs in writerOpts), so the 3.1.1 release was replayed with both versions:

• semantic-release 25.0.9 programmatic API in dry-run mode on 511efc8 (the commit released as 3.1.1), with the real release.config.js minus @semantic-release/github (needs a token, does not generate notes), a local copy of the repository and no credentials. semantic-release loaded the single hoisted plugin copy (14.1.0 or 14.1.1) and conventional-changelog-writer 8.0.0.
• nextRelease.notes with 14.1.0, with 14.1.1, and the published 3.1.1 release body are byte-identical: 347 bytes, sha256 a60e175b769358b275a93d5c1f7952b537ced3f8c5149075abbe00e9569b1ce5.
• Direct generateNotes calls with the same plugin options give identical output with both versions (7,347 bytes, dates normalized, sha256 f0b9e9b7f8ee5c4e077088e43a699774979b14b23564bf2aca6be60b95643f4a) for these scenarios:
  • patch 1.2.4, minor 1.3.0 and major 2.0.0 releases
  • first release 1.0.0 without a compare link
  • empty commit list
  • commits with scopes, Closes #N and cross-repository issue references, BREAKING CHANGE notes, and markdown, HTML, handlebars-like and unicode text

Summary by CodeRabbit

• Chores
  • Updated release tooling. This maintenance change does not alter the app’s user-facing features or behavior. No changes to the public interface are included.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: f2c5ba2b-e2c9-45fa-96ee-6902b49c1771

Commits

Reviewing files that changed from the base of the PR and between 1cce959 and d16375f.

Files selected for processing: 2

• package-lock.json
• package.json

Included review availability: This review used your included allowance. Your plan provides up to 5 included reviews per hour; 3 remain after this review.

Walkthrough

The development dependency @semantic-release/release-notes-generator changes from version 14.1.0 to 14.1.1. The lockfile updates its package records and removes four transitive package entries.

Changes: Release-notes generator dependency update

Layer / File(s)	Summary
Update the release-notes generator dependency package.json, package-lock.json	@semantic-release/release-notes-generator changes to version 14.1.1. The lockfile removes from2, get-stream, into-stream, and p-is-promise entries from its package records and legacy dependency map.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: Minimal · up to d1637

This dependency-only update introduces no identified merge-blocking risk.

Pre-merge checks: 7

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title starts with the allowed refactor: prefix, uses a capitalized first letter in the description, and accurately describes the dependency upgrade.
Linked Issues check		Issue #919 requires the package upgrade. package.json changes @semantic-release/release-notes-generator from 14.1.0 to 14.1.1. package-lock.json records version 14.1.1, its integrity, and …
Out of Scope Changes check		The pull request changes only the dependency declaration and its lockfile records. The lockfile changes directly support the upgrade in issue #919. No unrelated source, test, configuration, or documen…
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Security Check		PASS. The pull request changes only the development dependency version and its lockfile records. It adds no application code, scripts, permissions, URLs, or input-handling logic. The updated package r…
Engage In Review Feedback		PASS. The supplied review data reports zero actionable findings in the current review and no posted CodeRabbit review threads. There was no review feedback that required discussion, implementation, or…

Full details: Linked Issues check

Explanation

Issue #919 requires the package upgrade. package.json changes @semantic-release/release-notes-generator from 14.1.0 to 14.1.1. package-lock.json records version 14.1.1, its integrity, and the matching dependency changes. The lockfile removes the obsolete get-stream, into-stream, from2, and p-is-promise entries. Issue #919 defines no additional coding or automated-test requirement.

Full details: Out of Scope Changes check

Explanation

The pull request changes only the dependency declaration and its lockfile records. The lockfile changes directly support the upgrade in issue #919. No unrelated source, test, configuration, or documentation changes appear in the reviewed diff.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Full details: Security Check

Explanation

PASS. The pull request changes only the development dependency version and its lockfile records. It adds no application code, scripts, permissions, URLs, or input-handling logic. The updated package remains marked dev-only, and the lockfile removes the prior get-stream, into-stream, from2, and p-is-promise entries. No security-sensitive code pattern is introduced by this diff.

Full details: Engage In Review Feedback

Explanation

PASS. The supplied review data reports zero actionable findings in the current review and no posted CodeRabbit review threads. There was no review feedback that required discussion, implementation, or retraction.

Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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