Release Guide

Release Checklist

This checklist contains the set of tasks that should be completed before every release. An issue should be created prior to the start of the work on the next release with the contents below. The issue should then be pinned in the repo for easy discoverability. Each task should have an assignee. This should be indicated by adding the GitHub username of the assigned dev next to the task like this: (). Before Preview

• Draft GitHub release notes from commit log
• Promote canary build to preview using wiki instructions
• Push build to stable branch
  • Enable CI schedule for new branch of CI pipeline
  • Update dashboard @ms with an entry for CI ${version}
  • Add release schedule for the new stable branch of publish pipline
  • Update dashboard @microsoft with an entry for Publish ${version}
• Update GitHub release notes to use manually curated notes instead of a changelog
• Post release notes internally

---

After Preview

• Move most issues targeting current release
• Test updated gallery app using wiki instructions
• Check CI Runs for Upgrading Sample Apps (@jonthysell )
• Snap Hermes-Windows release
• Do a pass on API Docs using wiki instructions
• Integrate any applicable patch/prerelease releases for React Native

---

Before Release

• Ensure doc issues are addressed
• Promote latest build to legacy using wiki instructions

---

Release

• Update preview release notes with any changes from cherry-picked PRs
• Update samples
• Update React Native Gallery
• Publish React Native Gallery
• Promote preview build to latest using wiki instructions
• Update GitHub release notes to use manually curated notes instead of a changelog
• Update website
• Send out internal release announcement
• Update CI to use /apiVersion 0.XX -- After Website Updated
• Ensure Accessibility is tested through updated Gallery