Add script to apply release-only changes

[guangy10]

Stack from ghstack (oldest at bottom):

• -> Add script to apply release-only changes #2578
• Add script to cut release branch #2567

Differential Revision: D55226326

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/2578

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 959f497 with merge base ec6b88a ():

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest / macos (buck2) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[guangy10]

@huydhn Should we update the pinned pytorch to a released version, e.g. 2.3.0 in .ci/docker/ci_commit_pins/pytorch.txt? Otherwise how do we guarantee the executorch 0.2.0 will be compatible with 2.3.0?

[guangy10]

@guangy10 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[huydhn]

@huydhn Should we update the pinned pytorch to a released version, e.g. 2.3.0 in .ci/docker/ci_commit_pins/pytorch.txt? Otherwise how do we guarantee the executorch 0.2.0 will be compatible with 2.3.0?

This's a good idea, but I think let do that release-only in a separate PR for now. As I'm not quite sure what form it should looks like yet. I think it should just be changing the pinned commit to the branch release/2.3, but I suspect that the checkout logic needs to be updated accordingly.

Once we have that release-only change done once, we could figure out if it's possible to enhance this script to do that automatically.

[facebook-github-bot]

@guangy10 merged this pull request in e7748f8.