Skip to content

refactor: Bump @semantic-release/github from 12.0.6 to 12.0.9#268

Merged
mtrezza merged 1 commit into
parse-community:mainfrom
mtrezza:refactor/semantic-release-github-12.0.9
Jul 20, 2026
Merged

refactor: Bump @semantic-release/github from 12.0.6 to 12.0.9#268
mtrezza merged 1 commit into
parse-community:mainfrom
mtrezza:refactor/semantic-release-github-12.0.9

Conversation

@mtrezza

@mtrezza mtrezza commented Jul 20, 2026

Copy link
Copy Markdown
Member

Closes #266

Changes

Bumps the direct devDependency @semantic-release/github from 12.0.6 to 12.0.9.

Breaking

None. This is a patch-level bump of a devDependency used only in the release pipeline; it does not affect the published package or its runtime.

Code Changes

  • package.json: @semantic-release/github 12.0.612.0.9.
  • package-lock.json: updated the @semantic-release/github subtree — its http-proxy-agent/https-proxy-agent deps move to ^9, pulling in agent-base@9 and the new proxy-agent-negotiate.

Summary by CodeRabbit

  • Chores
    • Updated the GitHub release automation tooling and related networking packages to newer versions.
    • Improved compatibility with current package and runtime requirements.

@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 20, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@mtrezza, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 22 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 80354916-0ea6-4a88-9ce6-c85a421c926a

📥 Commits

Reviewing files that changed from the base of the PR and between 4f0c8a1 and 6cef7c8.

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

Walkthrough

Changes

Semantic release dependency upgrade

Layer / File(s) Summary
Update semantic-release package version
package.json, package-lock.json
The development dependency and locked package metadata update @semantic-release/github from 12.0.6 to 12.0.9.
Refresh proxy dependency graph
package-lock.json
Proxy agents upgrade to 9.1.0, agent-base to 9.0.0, and proxy-agent-negotiate is added with Node and optional peer dependency metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes


Caution

Pre-merge checks failed

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

  • Ignore

❌ Failed checks (1 error, 1 inconclusive)

Check name Status Explanation Resolution
Description check ❌ Error The description covers the issue and change, but it does not follow the repository template headings for Pull Request, Issue, Approach, and Tasks. Reformat the PR description to match the template, adding the Pull Request, Issue, Approach, and Tasks sections with the required content.
Engage In Review Feedback ❓ Inconclusive Repo shows only the bump commit; no review-comment or discussion artifacts are present to confirm feedback engagement. Need PR conversation or review-comment history showing feedback was discussed and either addressed in a commit or retracted.
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the PR change and uses an allowed prefix with a clear summary.
Linked Issues check ✅ Passed The PR updates @semantic-release/github from 12.0.6 to 12.0.9 in package.json and package-lock.json as requested by #266.
Out of Scope Changes check ✅ Passed The extra lockfile dependency updates are transitive changes required by the requested version bump, with no unrelated edits shown.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check ✅ Passed Only dependency bumps; no code changes. GitHub advisories affect http-proxy-agent <2.1.0 and https-proxy-agent <2.2.3, while PR upgrades to 9.1.0.
✨ 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.

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (4f0c8a1) to head (6cef7c8).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #268   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          159       159           
=========================================
  Hits           159       159           

☔ 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 20, 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 20, 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-api-mail-adapter"
pr="268"

echo "=== PR metadata ==="
gh pr view "$pr" --repo "$repo" --json state,isDraft,mergeable,reviewDecision,baseRefName,headRefName,comments,reviews \
  --jq '{state,isDraft,mergeable,reviewDecision,baseRefName,headRefName, reviews: [.reviews[] | {author: .author.login, state, body}], comments: [.comments[] | {author: .author.login, body}]}'

echo "=== Review comments (including resolution status) ==="
gh api "repos/$repo/pulls/$pr/comments?per_page=100" \
  --jq '.[] | {id, user: .user.login, path, line, side, body, in_reply_to_id, created_at}'

echo "=== Changed files ==="
gh pr diff "$pr" --repo "$repo" --name-only

echo "=== Final diff ==="
gh pr diff "$pr" --repo "$repo" -- package.json package-lock.json

Length of output: 11688


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== PR diff against main ==="
git diff --no-ext-diff --unified=40 origin/main...HEAD -- package.json package-lock.json

echo "=== Lockfile consistency ==="
python3 - <<'PY'
import json
from pathlib import Path

manifest = json.loads(Path("package.json").read_text())
lock = json.loads(Path("package-lock.json").read_text())

name = "`@semantic-release/github`"
expected = manifest.get("devDependencies", {}).get(name)
root = lock.get("packages", {}).get("", {}).get("devDependencies", {}).get(name)
entry = lock.get("packages", {}).get("node_modules/@semantic-release/github", {})

print(f"package.json devDependency: {expected!r}")
print(f"package-lock root devDependency: {root!r}")
print(f"installed lockfile version: {entry.get('version')!r}")
print(f"installed lockfile resolved: {entry.get('resolved')!r}")
print(f"manifest/root match: {expected == root}")
print(f"installed version satisfies exact expected version: {entry.get('version') == expected}")
print("direct dependencies:")
for dep, spec in sorted(entry.get("dependencies", {}).items()):
    print(f"  {dep}: {spec}")
PY

echo "=== Relevant nested package entries ==="
python3 - <<'PY'
import json
from pathlib import Path

lock = json.loads(Path("package-lock.json").read_text())
for path, entry in sorted(lock.get("packages", {}).items()):
    if any(token in path for token in (
        "node_modules/@semantic-release/github",
        "node_modules/http-proxy-agent",
        "node_modules/https-proxy-agent",
        "node_modules/agent-base",
        "node_modules/proxy-agent-negotiate",
    )):
        print(f"{path}: version={entry.get('version')!r}, dependencies={entry.get('dependencies', {})}")
PY

Length of output: 24849


@mtrezza Approved. The update is limited to the requested devDependency and its required lockfile subtree; the manifest and lockfile consistently resolve @semantic-release/github to 12.0.9. No unresolved review feedback or additional changes are indicated.

[approve]

@mtrezza

mtrezza commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
✅ Action performed

Full review finished.


Your plan includes PR reviews subject to rate limits. More reviews will be available in 18 minutes.

@mtrezza

mtrezza commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
✅ Action performed

Full review finished.

@mtrezza

mtrezza commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
✅ Action performed

Full review finished.


Your plan includes PR reviews subject to rate limits. More reviews will be available in 22 minutes.

@mtrezza
mtrezza merged commit ecdd7b4 into parse-community:main Jul 20, 2026
9 of 10 checks passed
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