Skip to content

refactor: Bump @semantic-release/release-notes-generator from 14.1.0 to 14.1.1#10587

Merged
mtrezza merged 1 commit into
parse-community:alphafrom
mtrezza:refactor/semantic-release-release-notes-generator-14.1.1
Jul 19, 2026
Merged

refactor: Bump @semantic-release/release-notes-generator from 14.1.0 to 14.1.1#10587
mtrezza merged 1 commit into
parse-community:alphafrom
mtrezza:refactor/semantic-release-release-notes-generator-14.1.1

Conversation

@mtrezza

@mtrezza mtrezza commented Jul 19, 2026

Copy link
Copy Markdown
Member

Closes #10585

Replacement PR for the Dependabot bump of @semantic-release/release-notes-generator (direct devDependency) from 14.1.0 to 14.1.1.

Changes

  • Bumps @semantic-release/release-notes-generator from 14.1.0 to 14.1.1 (patch).
  • Upstream changelog: fix(deps): update dependency get-stream to v9 (v14.1.0...v14.1.1). The published 14.1.1 no longer declares get-stream/into-stream as direct dependencies, so the lockfile drops the previously-nested get-stream@7.0.1; the change is fully scoped to this package.

Breaking Changes

  • None. Patch release; dev-only release-tooling dependency (used by semantic-release), no impact on project runtime code.

Code Changes Required

  • None. Only package.json and package-lock.json changed.

Summary by CodeRabbit

  • Chores
    • Updated the release notes generation tooling to version 14.1.1.
    • Refreshed locked dependency metadata to ensure consistent installations.

@parse-github-assistant

Copy link
Copy Markdown

🚀 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

coderabbitai Bot commented Jul 19, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The development dependency @semantic-release/release-notes-generator is upgraded from 14.1.0 to 14.1.1, and package-lock.json is refreshed with new package metadata and dependency requirements.

Changes

Release notes generator update

Layer / File(s) Summary
Dependency declaration and lockfile update
package.json, package-lock.json
The development dependency and locked package are updated to 14.1.1, with refreshed resolved/integrity metadata and removal of obsolete get-stream and into-stream entries.

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

Suggested reviewers: semantic-release-bot


Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

  • Ignore

❌ Failed checks (1 error)

Check name Status Explanation Resolution
Engage In Review Feedback ❌ Error The review note was not acted on: package-lock.json still contains the stale @saithodev/semantic-release-backmerge subtree with release-notes-generator 12.1.0/get-stream 7.0.1. Refresh that nested lockfile subtree (or discuss with the reviewer and get the comment retracted) before resolving the feedback.
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the required prefix and clearly summarizes the dependency bump.
Description check ✅ Passed The PR includes the issue, change summary, and impact, but it does not follow the repository's exact Issue/Approach/Tasks template.
Linked Issues check ✅ Passed The changes satisfy #10585 by bumping the package to 14.1.1 and reflecting the upstream get-stream v9 dependency update.
Out of Scope Changes check ✅ Passed Only the two expected dependency files changed, and the edits stay within the version-bump scope.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check ✅ Passed Only a dev-only dependency bump and lockfile refresh; no new code paths or GitHub-advisory-backed vuln patterns surfaced.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

coderabbitai[bot]
coderabbitai Bot previously requested changes Jul 19, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 81: Refresh the package-lock.json dependency subtree for
`@saithodev/semantic-release-backmerge` so its nested
`@semantic-release/release-notes-generator` matches the package.json pin 14.1.1,
including updated get-stream and into-stream versions; regenerate the lockfile
rather than editing only the top-level manifest.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 98437d80-ced7-42fc-b59e-98a860e0b6fa

📥 Commits

Reviewing files that changed from the base of the PR and between c6fd388 and dfe1119.

📒 Files selected for processing (2)
  • package-lock.json
  • package.json

Comment thread package.json
@codecov

codecov Bot commented Jul 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.69%. Comparing base (629426f) to head (dfe1119).
⚠️ Report is 1 commits behind head on alpha.

Additional details and impacted files
@@           Coverage Diff           @@
##            alpha   #10587   +/-   ##
=======================================
  Coverage   92.69%   92.69%           
=======================================
  Files         193      193           
  Lines       17027    17027           
  Branches      248      248           
=======================================
  Hits        15784    15784           
  Misses       1222     1222           
  Partials       21       21           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mtrezza

mtrezza commented Jul 19, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai approve the PR if all review feedback is addressed and there is nothing else to do.

@coderabbitai

coderabbitai Bot commented Jul 19, 2026

Copy link
Copy Markdown

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="parse-community/parse-server"
pr_number="10587"

echo "== PR metadata =="
gh pr view "$pr_number" --repo "$repo" --json state,isDraft,mergeStateStatus,reviewDecision,statusCheckRollup,files \
  --jq '{state, isDraft, mergeStateStatus, reviewDecision, files: [.files[].path]}'

echo
echo "== Reviews =="
gh api "repos/$repo/pulls/$pr_number/reviews?per_page=100" \
  --jq '.[] | {user: .user.login, state, submitted_at, body}'

echo
echo "== Issue comments =="
gh api "repos/$repo/issues/$pr_number/comments?per_page=100" \
  --jq '.[] | {user: .user.login, created_at, body}'

echo
echo "== Review comments =="
gh api "repos/$repo/pulls/$pr_number/comments?per_page=100" \
  --jq '.[] | {id, user: .user.login, path, line, original_line, body, created_at}'

echo
echo "== Exact PR diff =="
gh pr diff "$pr_number" --repo "$repo" -- package.json package-lock.json

Length of output: 20216


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="parse-community/parse-server"
pr_number="10587"

echo "== Changed manifest declaration =="
jq -r '.devDependencies["`@semantic-release/release-notes-generator`"]' package.json

echo
echo "== Relevant lockfile entries =="
jq '{
  lockfileVersion,
  root_generator: .packages[""].devDependencies["`@semantic-release/release-notes-generator`"],
  direct_generator: .packages["node_modules/@semantic-release/release-notes-generator"]
    | {version, dependencies},
  backmerge: .packages["node_modules/@saithodev/semantic-release-backmerge"]
    | {version, dependencies},
  nested_generator: .packages["node_modules/@saithodev/semantic-release-backmerge/node_modules/@semantic-release/release-notes-generator"]
    | {version, dependencies},
  nested_get_stream: .packages["node_modules/@saithodev/semantic-release-backmerge/node_modules/@semantic-release/release-notes-generator/node_modules/get-stream"]
    | {version, dependencies},
  nested_into_stream: .packages["node_modules/@saithodev/semantic-release-backmerge/node_modules/@semantic-release/release-notes-generator/node_modules/into-stream"]
    | {version, dependencies}
}' package-lock.json

echo
echo "== Lockfile JSON validation =="
jq -e 'type == "object" and .lockfileVersion >= 1 and (.packages | type == "object")' package-lock.json >/dev/null
echo "valid"

echo
echo "== PR checks =="
gh pr checks "$pr_number" --repo "$repo" --json name,state,link --jq '.[] | {name,state,link}'

echo
echo "== File diff stats =="
git diff --stat HEAD^ HEAD -- package.json package-lock.json

Length of output: 6780


@mtrezza Approved. The nested v12.1.0 generator is independently required through @saithodev/semantic-release-backmerge’s semantic-release@^22 dependency tree; it should not be forced to match the direct v14.1.1 pin. The lockfile is valid and all CI checks are passing.

[approve]

@mtrezza

mtrezza commented Jul 19, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai approve the PR if all review feedback is addressed and there is nothing else to do.

@coderabbitai

coderabbitai Bot commented Jul 19, 2026

Copy link
Copy Markdown

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="parse-community/parse-server"
pr_number="10587"

echo "== Pull request state =="
gh pr view "$pr_number" --repo "$repo" \
  --json state,isDraft,mergeStateStatus,reviewDecision,headRefOid \
  --jq '{state, isDraft, mergeStateStatus, reviewDecision, headRefOid}'

echo
echo "== Check status =="
gh pr checks "$pr_number" --repo "$repo" --json name,state,link \
  --jq '.[] | {name, state, link}'

echo
echo "== CodeRabbit review comments =="
gh api "repos/$repo/pulls/$pr_number/comments?per_page=100" --paginate \
  --jq '.[] | select(.user.login == "coderabbitai" or .user.login == "coderabbitai[bot]") | {id, path, line, original_line, body, created_at}'

echo
echo "== CodeRabbit top-level comments =="
gh api "repos/$repo/issues/$pr_number/comments?per_page=100" --paginate \
  --jq '.[] | select(.user.login == "coderabbitai" or .user.login == "coderabbitai[bot]") | {id, body, created_at}'

Length of output: 21390


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="parse-community/parse-server"
pr_number="10587"

echo "== Reviews (chronological) =="
gh api "repos/$repo/pulls/$pr_number/reviews?per_page=100" --paginate \
  --jq '.[] | {id, user: .user.login, state, commit_id, submitted_at, body}'

echo
echo "== Requested reviewers and merge requirements =="
gh pr view "$pr_number" --repo "$repo" \
  --json reviewRequests,latestReviews,mergeStateStatus,reviewDecision \
  --jq '{reviewRequests, latestReviews, mergeStateStatus, reviewDecision}'

echo
echo "== Base branch protection =="
base_branch=$(gh pr view "$pr_number" --repo "$repo" --json baseRefName --jq -r '.baseRefName')
gh api "repos/$repo/branches/$base_branch/protection" \
  --jq '{required_status_checks, required_pull_request_reviews, required_linear_history, required_conversation_resolution}' \
  2>/dev/null || echo "Branch-protection details unavailable."

Length of output: 4146


@mtrezza Approved. All CI checks pass, and the sole CodeRabbit finding was explicitly withdrawn as invalid. The remaining Changes requested status is the stale original CodeRabbit review event—not unresolved feedback.

[approve]

@mtrezza
mtrezza dismissed coderabbitai[bot]’s stale review July 19, 2026 14:54

CodeRabbit investigated and explicitly withdrew this finding as invalid ('You are correct... I'm withdrawing the finding') and posted 'Approved'. This is the stale original review event; all CI is green. Dismissing to reflect resolved state.

@mtrezza
mtrezza merged commit 0ebd935 into parse-community:alpha Jul 19, 2026
25 checks passed
@mtrezza
mtrezza deleted the refactor/semantic-release-release-notes-generator-14.1.1 branch July 19, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant