chore: back-merge main into develop after v2.3(Verawood.1)

[IvanStepanok]

Brings develop back in line with main after the Verawood release.

develop is strictly behind — 9 commits, nothing ahead — so this is a clean catch-up with no conflicts.

What it carries over

• chore: pin GitHub Actions workflows to full commit SHAs #660, which pinned the third-party actions in swiftlint.yml, unit_tests.yml and validate-translations.yml to full commit SHAs. It landed on main only, so develop still refers to those actions by tag.
• The v2.3(Verawood.1) release merge commit itself.

Why it matters now

main and develop had been drifting since 2026-05-28. #660 touched the same two workflow files that #666 rewrote during the release, and that was resolved once, in the release merge — cleanly, because the two changed different lines. Leaving develop behind means the next release merge would have to resolve the same overlap again, against a develop that has moved on further.

Verified on main after the release merge: both changes survived — the actions are SHA-pinned and ruby/setup-ruby with ruby-version: 3.3 and xcodes select 26.2 are present.

[openedx-webhooks]

Thanks for the pull request, @IvanStepanok!

This repository is currently maintained by @openedx/openedx-mobile-maintainers.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (0c72bd4) to head (4cbcb46).

Additional details and impacted files

@@      Coverage Diff       @@
##   develop   #668   +/-   ##
==============================
==============================

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.