feat(updater): Add post-update-script support

[vaind]

Summary

Add support for running custom scripts after dependency updates, enabling additional repository modifications before PR creation.

Changes

• New input parameter: post-update-script - accepts path to bash (.sh) or PowerShell (.ps1) script
• Script execution: Scripts receive two arguments:
  • $1 / $args[0] - Original version (before update)
  • $2 / $args[1] - New version (after update)
• Integration: Post-update logic added to update-dependency.ps1
• Tests: Comprehensive unit tests covering both script types and error cases
• Documentation: README updated with usage examples

Use Cases

This feature enables workflows like:

• Updating lock files after dependency version changes
• Running code generators that depend on updated dependencies
• Modifying configuration files that reference dependency versions
• Applying project-specific transformations

Usage Example

- uses: getsentry/github-workflows/updater@v3
  with:
    path: modules/sentry-cocoa
    name: Cocoa SDK
    post-update-script: scripts/update-lockfile.sh
    api-token: ${{ secrets.CI_DEPLOY_KEY }}

Bash script (scripts/update-lockfile.sh):

#!/usr/bin/env bash
set -euo pipefail

ORIGINAL_VERSION="$1"
NEW_VERSION="$2"

echo "Updated from $ORIGINAL_VERSION to $NEW_VERSION"
# Update lock files or make other changes

Test Plan

• Unit tests for PowerShell script execution
• Unit tests for bash script execution
• Unit tests for error handling (missing script, script failures)
• Unit tests for empty original version case

🤖 Generated with Claude Code

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against ff0be35