Skip to content

refactor: Bump semantic-release from 25.0.8 to 25.0.9 - #615

Merged
mtrezza merged 1 commit into
parse-community:masterfrom
mtrezza:refactor/semantic-release-25.0.9
Sep 26, 2026
Merged

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

Conversation

@mtrezza

@mtrezza mtrezza commented Sep 26, 2026

Copy link
Copy Markdown
Member

Issue

Closes #607

Approach

Upgrades the dev dependency semantic-release from 25.0.8 to 25.0.9. The lock file changes are limited to semantic-release itself; its dependency list and version ranges are unchanged from 25.0.8, and the installed @semantic-release/* plugins already satisfy its ranges.

Changes

See the semantic-release v25.0.9 release notes.

Breaking Changes

None. This is a patch release with a single bug fix. The Node.js requirement (^22.14.0 || >= 24.10.0) is unchanged from 25.0.8; semantic-release only runs in the release-automated workflow, which uses Node.js 24.

Code Changes Required

None — the upgrade is a drop-in replacement.

Tasks

No tasks apply; this PR only changes a dev dependency.

@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 Sep 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

  • Ask an admin to enable usage-based reviews

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Next included review available in 54 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 65 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 19b8744a-c294-48dd-b5ba-54e23deb1e49

📥 Commits

Reviewing files that changed from the base of the PR and between b53343b and 0ce0e39.

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

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

@codecov

codecov Bot commented Sep 26, 2026

Copy link
Copy Markdown

Codecov Report

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

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #615   +/-   ##
=======================================
  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 3eb1cf7 into parse-community:master Sep 26, 2026
9 checks passed
@mtrezza
mtrezza deleted the refactor/semantic-release-25.0.9 branch September 26, 2026 01:29
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