Skip to content

Conversation

@gziolo
Copy link
Member

@gziolo gziolo commented Oct 14, 2025

Similar process as with #90.

This PR prepares the branch to release v0.3.0 based on the work accomplished in pre WP 6.9 milestone:

  • Replaces @since n.e.x.t with @since 0.3.0
  • Bumps version from 0.2.0 to 0.3.0
  • Includes coding style fixes necessary to pass CI check in WordPress core.

The same version was tested against WP core with WordPress/wordpress-develop#9410 and all CI checks passed with the changes applied.

@gziolo gziolo self-assigned this Oct 14, 2025
@gziolo gziolo added the [Type] Developer Documentation Improvements or additions to documentation label Oct 14, 2025
@gziolo gziolo added this to the pre WP 6.9 milestone Oct 14, 2025
@codecov
Copy link

codecov bot commented Oct 14, 2025

Codecov Report

❌ Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 86.65%. Comparing base (9ffcc0e) to head (5bb3a3e).
⚠️ Report is 1 commits behind head on trunk.

Files with missing lines Patch % Lines
includes/bootstrap.php 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff            @@
##              trunk     #116   +/-   ##
=========================================
  Coverage     86.65%   86.65%           
  Complexity      148      148           
=========================================
  Files            18       18           
  Lines           982      982           
  Branches         92       92           
=========================================
  Hits            851      851           
  Misses          131      131           
Flag Coverage Δ
javascript 93.04% <ø> (ø)
unit 84.70% <88.88%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.

@gziolo gziolo marked this pull request as ready for review October 14, 2025 14:19
@github-actions
Copy link

github-actions bot commented Oct 14, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: emdashcodes <emdashcodes@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link
Contributor

@emdashcodes emdashcodes left a comment

Choose a reason for hiding this comment

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

Looks good. Confirmed the PR only contains version updates and a few minor spacing fixes.

@gziolo gziolo requested a review from a team October 14, 2025 14:47
@gziolo gziolo merged commit c1b24b8 into trunk Oct 14, 2025
39 checks passed
@gziolo gziolo deleted the update/prepare-v0.3.0-release branch October 14, 2025 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Developer Documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants