fix: Prevent rollback steps from running when not needed

[cameronrye]

Problem

After merging the build verification improvements, the actual release (run #3) failed because the rollback steps were incorrectly evaluating their conditions. The "Rollback on publish failure" step ran even though the publish succeeded, causing the workflow to fail.

Root Cause

The rollback steps had incomplete conditional logic:

if: steps.publish.outcome == 'failure'

This condition was missing the !inputs.dry_run check. When steps were skipped due to dry run mode, the rollback conditions were evaluating incorrectly.

Solution

Updated both rollback step conditions to include the dry run check:

- name: Rollback on push failure
  if: ${{ !inputs.dry_run && steps.push.outcome == 'failure' }}

- name: Rollback on publish failure
  if: ${{ !inputs.dry_run && steps.publish.outcome == 'failure' }}

This ensures rollback steps only run when:

1. Not in dry run mode
2. The corresponding step actually failed

Changes in this PR

This PR includes two commits:

1. Enhanced build verification (from previous PR fix: Enhance build verification in CI and release workflows #15)
2. Fixed rollback logic (new fix)

Testing

• Dry run completed successfully (run ci: bump actions/checkout from 4 to 5 #2)
• Actual release failed due to rollback logic issue (run ci: bump actions/setup-node from 4 to 6 #3)
• Failed release was automatically rolled back
• Fix has been applied and is ready for testing

Next Steps

Once merged, you can retry the release and it should complete successfully without false rollback triggers.