Add optional package name arguments to wp package update

[Copilot]

• Understand the current implementation of wp package update command
• Review Composer's setUpdateAllowList() method to update specific packages
• Modify the update() method signature to accept optional package name arguments
• Add logic to handle specific package updates using setUpdateAllowList()
• Update command documentation/PHPDoc
• Add Behat tests for updating specific packages
• Address code review feedback
  • Updated method description to reflect it can update specific packages
  • Improved success message logic by extracting count check
• Address PR review feedback
  • Track actual package updates using Composer event listener
  • Provide accurate messaging when some packages don't have updates available
  • Handle cases where packages are already at latest version
• Run lint, phpcs, and phpstan checks (all pass)
• Run PHPUnit tests (all pass)
• Run CodeQL security check (no issues)
• Final verification complete

Summary

Successfully implemented optional package name arguments for wp package update command with full backward compatibility and accurate update tracking. The implementation now:

✅ Tracks actual package updates via Composer events
✅ Provides accurate success messages based on what was actually updated
✅ Handles scenarios where packages are already up to date
✅ Distinguishes between partial and full update success

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add package name argument to wp package update</issue_title>
<issue_description>The wp package update command updates all outdated packages. I'd like to be able to update one specific package like so:

wp package update vendor/package-name

I'm also tempted to suggest bringing it in line with the plugin update and theme update commands, which at minimum would...

• require one or more package name arguments (which, I acknowledge, breaks existing functionality, and is very bad)
• suggest the addition of an --all flag to re-implement the current behavior (wp package update --all)

Thoughts?</issue_description>

<agent_instructions>Add an optional positional argument for the wp package update command.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@swissspidy Let's start with supporting one or more packages to be updated, maintaining backward compatibility.

• Fixes Add package name argument to wp package update #207

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.