Brian Kane 06e1d20a74 fix: component dispatch with autoRevision=true for policy transforms ...

When policies retrigger with autoRevision=true, components were not
redeploying even though new ApplicationRevisions were created. The
dispatcher was comparing component properties against the NEW revision
(which already had policy transforms) instead of the PREVIOUS revision.

Changes:
- generator.go: Pass latestAppRev to generateDispatcher()
- dispatcher.go: Add previousAppRev parameter and conditional comparison
  logic based on autoRevision annotation
- When autoRevision=true: Compare against previous revision to detect
  policy-driven changes
- When autoRevision=false (default): Use existing logic for backward
  compatibility

Added documentation noting that the default comparison logic seems
unclear and may need future simplification.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2026-02-17 18:15:51 +00:00

..

2026-02-17-application-scoped-policies.md

fix: component dispatch with autoRevision=true for policy transforms

2026-02-17 18:15:51 +00:00