Skip to content

refactor: Bump @semantic-release/npm from 13.1.5 to 13.2.0 - #627

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

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

Conversation

@mtrezza

@mtrezza mtrezza commented Oct 17, 2026

Copy link
Copy Markdown
Member

Closes #617

Changes

  • 13.2.0: Added npm trusted publishing (OIDC token exchange) support for CircleCI (feat(trusted-publishing): add support for CircleCI semantic-release/npm#1212). The change is additive: a new CircleCI branch in the token exchange that is only taken when the plugin runs on CircleCI. The GitHub Actions and GitLab CI/CD code paths are unchanged, so this repository's release workflow (GitHub Actions with NPM_TOKEN) is unaffected. The plugin's runtime dependencies and Node.js engine range (^22.14.0 || >= 24.10.0) are unchanged from 13.1.5, and the plugin only runs in the release workflow on Node.js 24.
  • Lock file: only the @semantic-release/npm entry changes. Its bundled npm dependency stays at 11.20.0. All changes are development-only.

Breaking Changes

None

Code Changes Required

None — the upgrade is a drop-in replacement.

@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

Warning

Review limit reached

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.

  • 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 27 minutes.

Check out review usage here.

View limit details

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

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 7a816c9b-0959-4130-9d01-734bae4775ac
📥 Commits

Reviewing files that changed from the base of the PR and between e1f6aad and 07aca4b.

📒 Files selected for processing: 2
  • package-lock.json
  • package.json
  • 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 (e1f6aad) to head (07aca4b).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #627   +/-   ##
=======================================
  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 9fa49e6 into parse-community:master Oct 17, 2026
9 checks passed
@mtrezza
mtrezza deleted the refactor/semantic-release-npm-13.2.0 branch October 17, 2026 13:53
@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