Allow wcommon 2

[robbecker-wf]

Motivation

We'd like to be able to upgrade to w_common v2

Changes

Replace deprecated w_common calls with their equivalent v2 calls. These calls also exist in v1 so we can go ahead and leave these in for a patch release and raise the w_common max to allow w_common v2.

Review

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

Please review:

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

[aviary-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.

[robbecker-wf]

Ran a separate branch to run CI using w_common v2 #777

[greglittlefield-wf]

Just one question, otherwise LGTM.

• Changes look good
• CI passes in test branch

+10

[greglittlefield-wf]

+10

[greglittlefield-wf]

Closing and reopening to re-trigger Rosie

[greglittlefield-wf]

@rmconsole-wf

[greglittlefield-wf]

+10

[robbecker-wf]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM