Fix key and condition

[hunterbreathat-wk]

Motivation

A check wasn't updated after the change of step ordering, and a key was wrong.

Changes

• Update incorrect key name
• Update check

Release Notes

• Update incorrect key name
• Update check

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Frontend Frameworks Design member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary2-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[aaronlademann-wf]

+1

[aaronlademann-wf]

QA +1

🤞

@Workiva/release-management-pp

[aaronlademann-wf]

Semver +1

[rmconsole-wf]

+1 from RM