Skip to content

refactor: Bump @semantic-release/github from 12.0.9 to 12.0.10 - #626

Merged
mtrezza merged 1 commit into
parse-community:masterfrom
mtrezza:refactor/semantic-release-github-12.0.10
Oct 17, 2026
Merged

mtrezza merged 1 commit into
parse-community:masterfrom
mtrezza:refactor/semantic-release-github-12.0.10

Conversation

@mtrezza

@mtrezza mtrezza commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Closes #618

Changes

  • 12.0.10: Updated the @octokit/plugin-paginate-rest dependency from v14 to v15 (fix(deps): update dependency @octokit/plugin-paginate-rest to v15 semantic-release/github#1284). The plugin's own source code is unchanged. The only change in @octokit/plugin-paginate-rest 15.0.0 is the removal of the legacy (classic) Projects endpoints; @semantic-release/github only paginates GET /repos/{owner}/{repo}/pulls/{pull_number}/commits, so it is unaffected. The plugin's Node.js engine range is unchanged from 12.0.9 (^22.14.0 || >= 24.10.0), and the plugin only runs in the release workflow on Node.js 24.
  • Lock file: bumps @octokit/plugin-paginate-rest 14.0.0 to 15.0.0, and its nested @octokit/types 16.0.0 to 17.0.0 and @octokit/openapi-types 27.0.0 to 28.0.0. All are development-only.

Breaking Changes

None

Code Changes Required

None — the upgrade is a drop-in replacement.

Summary by CodeRabbit

  • Chores
    • Updated the project’s release tooling to newer versions. This maintenance update does not change the app’s features or behavior, and no changes to the user experience are included. The update applies to the tooling used during project releases; it does not add or remove any capabilities available in the app.

@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 Oct 17, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: bfbc4b1b-6e78-4cf9-8add-a07f9c92b43d
📥 Commits

Reviewing files that changed from the base of the PR and between b4c7b15 and a071017.

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

Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

📝 Walkthrough

The development dependency @semantic-release/github advances from 12.0.9 to 12.0.10. The lockfile updates its @octokit/plugin-paginate-rest dependency and the related @octokit/types and @octokit/openapi-types packages.

Changes: Semantic Release GitHub Dependency Update

Layer / File(s) Summary
Update semantic-release GitHub dependency
package.json, package-lock.json
@semantic-release/github advances to 12.0.10. The lockfile updates @octokit/plugin-paginate-rest to 15.0.0, @octokit/types to 17.0.0, and @octokit/openapi-types to 28.0.0.

Priority: ⬇️ Low

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

Merge Risk: ⚪ Minimal · up to a0710

This change updates release tooling dependencies without an established behavior or compatibility regression; it is mergeable subject to normal checks.

Pre-merge checks: Passed 7
Check name Status Explanation
Title check Passed The title begins with the allowed prefix "refactor:" and clearly describes the dependency upgrade. The change summary starts with a capitalized "Bump".
Description check Passed The description explains the issue, approach, dependency changes, impact, and breaking-change status. It does not use the template headings or include the task checklist, but it contains the main requ…
Linked Issues check Passed Issue [#618] requires @semantic-release/github to move from 12.0.9 to 12.0.10. package.json contains 12.0.10, and both lockfile representations resolve 12.0.10. The lockfile also updates the packa…
Out of Scope Changes check Passed The pull request changes only the @semantic-release/github declaration and its lockfile resolution data. The @octokit/plugin-paginate-rest, @octokit/types, and @octokit/openapi-types updates a…
Docstring Coverage Passed 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 Passed The pull request changes only package.json and package-lock.json. It upgrades the development-only @semantic-release/github package and its @octokit pagination/type packages. No application code, work…
Engage In Review Feedback Passed No review feedback comments or threads were returned, and the current review produced zero actionable findings. Therefore, no feedback was available for the user to ignore or resolve without engagemen…
Full details: Description check

Explanation

The description explains the issue, approach, dependency changes, impact, and breaking-change status. It does not use the template headings or include the task checklist, but it contains the main required information.

Full details: Linked Issues check

Explanation

Issue [#618] requires @semantic-release/github to move from 12.0.9 to 12.0.10. package.json contains 12.0.10, and both lockfile representations resolve 12.0.10. The lockfile also updates the package's required @octokit/plugin-paginate-rest dependency to 15.0.0 and its corresponding nested types packages.

Full details: Out of Scope Changes check

Explanation

The pull request changes only the @semantic-release/github declaration and its lockfile resolution data. The @octokit/plugin-paginate-rest, @octokit/types, and @octokit/openapi-types updates are transitive dependency changes required by the requested package upgrade. No unrelated source or configuration changes appear in the whole-pull-request 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

The pull request changes only package.json and package-lock.json. It upgrades the development-only @semantic-release/github package and its @octokit pagination/type packages. No application code, workflow, permissions, token handling, or runtime behavior changed. The lockfile records HTTPS registry URLs and integrity hashes for the new packages, and the diff passes validation. No problematic security pattern is introduced by this change.

Full details: Engage In Review Feedback

Explanation

No review feedback comments or threads were returned, and the current review produced zero actionable findings. Therefore, no feedback was available for the user to ignore or resolve without engagement.

✨ 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.

@codecov

codecov Bot commented Oct 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.18%. Comparing base (b4c7b15) to head (a071017).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #626   +/-   ##
=======================================
  Coverage   99.18%   99.18%           
=======================================
  Files          11       11           
  Lines        1841     1841           
=======================================
  Hits         1826     1826           
  Misses         15       15           

☔ 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 merged commit e1f6aad into parse-community:master Oct 17, 2026
9 checks passed
@mtrezza
mtrezza deleted the refactor/semantic-release-github-12.0.10 branch October 17, 2026 13:39
@parseplatformorg

Copy link
Copy Markdown
Contributor

🎉 This change has been released in version 8.5.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants