[fatadel]

Main | Deploy preview

Replace the first 4 steps of the deployment workflow with an automated interactive local script. It coordinates the l10n, CLI version, and production pull requests while preserving approvals, checks, and intended merge methods. Every step requires explicit confirmation.

This script was successfully tested during the October 13 deployment.

The 5th step will be handled as a follow-up.

Closes #5995

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.78%. Comparing base (7269a79) to head (c584118).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #6304    +/-   ##
========================================
  Coverage   84.78%   84.78%            
========================================
  Files         358      358            
  Lines       38946    38946            
  Branches    10917    11019   +102     
========================================
  Hits        33022    33022            
  Misses       5488     5488            
  Partials      436      436            

☔ 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.

[canova]

Thanks, adding drive by comments but will review a bit more carefully soon.

[canova]

Thanks for working on automating the deploymet! It's going to improve our lives a lot.

I think it would be great to add a --dry-run flag that prints each action that would change anything in GitHub or npm instead of really doing it. That would allow me or anyone to also test locally without having to worry about doing these. I was a bit scared to run it right now since I don't know what it would change. Could you add that?

[canova]

Does this handle merge queues?

[fatadel]

Yes, but for the happy path only for now.

[canova]

Ah, btw not for this PR but I thought it would be a nice improvement for later: there is a new terminal protocol getting popular (that only a few terminals implemented so far) to tell the status of the program: https://mitchellh.com/writing/program-status-osc7501
Currently only ghostty (unreleased version), rex (ghostty's new terminal), kitty (unreleased version), and iTerm2 etc. support. But looks like more terminals will start supporting in the future, it's especially useful for agents. It's a good way for an application to say "I'm waiting for an action"/ "I'm blocked", "I'm working", "I'm done" etc.

This is the doc of that OSC sequence: https://www.superlogical.com/rex/docs/build/program-status

[fatadel]

Thanks a lot for the very thorough review, @canova! I've now addressed all the comments you left, including adding the dry-run mode. Also, I re-wrote the whole thing in ts as it made things easier. That should not be a problem as we use node 24.