Skip to content

Update stable tag to 10.0.3 #59856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 21, 2025
Merged

Update stable tag to 10.0.3 #59856

merged 1 commit into from
Jul 21, 2025

Conversation

jorgeatorres
Copy link
Member

This PR updates the stable tag to 10.0.3

@github-actions github-actions bot added the plugin: woocommerce Issues related to the WooCommerce Core plugin. label Jul 21, 2025
@woocommercebot woocommercebot requested review from a team and joshuatf and removed request for a team July 21, 2025 17:11
Copy link
Contributor

Testing Guidelines

Hi @joshuatf ,

Apart from reviewing the code changes, please make sure to review the testing instructions (Guide) and verify that relevant tests (E2E, Unit, Integration, etc.) have been added or updated as needed.

Reminder: PR reviewers are required to document testing performed. This includes:

  • 🖼️ Screenshots or screen recordings.
  • 📝 List of functionality tested / steps followed.
  • 🌐 Site details (environment attributes such as hosting type, plugins, theme, store size, store age, and relevant settings).
  • 🔍 Any analysis performed, such as assessing potential impacts on environment attributes and other plugins, conducting performance profiling, or using LLM/AI-based analysis.

⚠️ Within the testing details you provide, please ensure that no sensitive information (such as API keys, passwords, user data, etc.) is included in this public issue.

Copy link
Contributor

coderabbitai bot commented Jul 21, 2025

📝 Walkthrough

Walkthrough

The stable version tag in the WooCommerce plugin's readme file was updated from 10.0.2 to 10.0.3. No other content or functionality was changed.

Changes

File(s) Change Summary
plugins/woocommerce/readme.txt Updated stable version tag from 10.0.2 to 10.0.3

Estimated code review effort

1 (~2 minutes)


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a73680 and c38e777.

📒 Files selected for processing (1)
  • plugins/woocommerce/readme.txt (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: jorgeatorres
PR: woocommerce/woocommerce#59675
File: .github/workflows/release-bump-as-requirement.yml:48-65
Timestamp: 2025-07-15T15:39:21.856Z
Learning: In WooCommerce core repository, changelog entries for all PRs live in `plugins/woocommerce/changelog/` directory and are processed during releases, not at the repository root level.
Learnt from: prettyboymp
PR: woocommerce/woocommerce#59048
File: .github/workflows/cherry-pick-milestoned-prs.yml:60-83
Timestamp: 2025-06-26T12:45:40.709Z
Learning: WooCommerce uses WordPress versioning conventions where minor versions in X.Y.Z format are constrained to 0-9 (Y cannot exceed 9). This means version increment logic should reset minor to 0 and increment major when minor reaches 9, rather than allowing two-digit minor versions like 9.10 or 9.11.
plugins/woocommerce/readme.txt (2)

Learnt from: jorgeatorres
PR: #59675
File: .github/workflows/release-bump-as-requirement.yml:48-65
Timestamp: 2025-07-15T15:39:21.856Z
Learning: In WooCommerce core repository, changelog entries for all PRs live in plugins/woocommerce/changelog/ directory and are processed during releases, not at the repository root level.

Learnt from: prettyboymp
PR: #59048
File: .github/workflows/cherry-pick-milestoned-prs.yml:60-83
Timestamp: 2025-06-26T12:45:40.709Z
Learning: WooCommerce uses WordPress versioning conventions where minor versions in X.Y.Z format are constrained to 0-9 (Y cannot exceed 9). This means version increment logic should reset minor to 0 and increment major when minor reaches 9, rather than allowing two-digit minor versions like 9.10 or 9.11.

@@ -4,7 +4,7 @@ Tags: online store, ecommerce, shop, shopping cart, sell online
Requires at least: 6.7
Tested up to: 6.8
Requires PHP: 7.4
Stable tag: 10.0.2
Stable tag: 10.0.3
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Verify consistency of version bump across the codebase

Stable tag now reads 10.0.3; double-check that every other version reference (plugin header Version:, WC_VERSION constant, packaging scripts, CI workflows, docs) is also set to 10.0.3 to prevent mismatched package metadata at release time.


🏁 Script executed:

#!/bin/bash
# Scan the repository for lingering 10.0.2 references
rg -n '10\.0\.2'

Length of output: 15291


Update all lingering “10.0.2” references to “10.0.3”

The grep scan for 10.0.2 shows many remaining occurrences that must be updated or regenerated to avoid mismatched metadata at release time:

  • pnpm-lock.yaml – numerous patch entries for @wordpress/data@10.0.2 and related deps (regenerate after bumping dependencies)
  • plugins/woocommerce/client/blocks/readme.txt (line 1027: = 10.0.2 - 2023-04-19 =)
  • plugins/woocommerce/client/blocks/docs/internal-developers/testing/releases/README.md (links to [10.0.2](./1002.md))
  • plugins/woocommerce/client/blocks/docs/internal-developers/testing/releases/1002.md (header # … release 10.0.2)
  • package.json (patch path: "@wordpress/data@10.0.2": "bin/patches/@wordpress__data@10.0.2.patch")
  • changelog.txt (entry = 10.0.2 2025-07-14 = and inline notes)

Please bump these to 10.0.3, update any packaging or CI workflows, regenerate your lockfile, and verify that Version: in the PHP plugin header and the WC_VERSION constant also reflect 10.0.3.

🤖 Prompt for AI Agents
In plugins/woocommerce/readme.txt at line 7, the version tag is still set to
10.0.2 in various files and metadata. Update all references from 10.0.2 to
10.0.3 including pnpm-lock.yaml dependencies,
plugins/woocommerce/client/blocks/readme.txt at line 1027, internal developer
docs and release notes, package.json patch paths, and changelog.txt entries.
Also update the PHP plugin header Version and WC_VERSION constant to 10.0.3,
regenerate the lockfile, and verify packaging and CI workflows reflect the new
version.

@jorgeatorres jorgeatorres merged commit 1d33249 into trunk Jul 21, 2025
23 of 25 checks passed
@jorgeatorres jorgeatorres deleted the update/stable-tag-10.0.3 branch July 21, 2025 17:14
@github-actions github-actions bot added this to the 10.1.0 milestone Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugin: woocommerce Issues related to the WooCommerce Core plugin.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant