ci: prepare release script to run on v1.x branch

[pichlermarc]

Which problem is this PR solving?

Once we merge next into main, we'll need to continue publishing on v1.x.
This PR prepares the release scripts to do that. I'll re-target to the v1.x branch once we have set it up.

Steps:

• chore: prepare next release #5274
• [next] merge changes from main #5275
• create v1.x branch
• re-target this PR to v1.x
• merge this PR

Then we can

• merge next to main (the other way around for once)

From then on we can continue backporting to and releasing from v1.x, independently of what's on main

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.66%. Comparing base (616d27a) to head (8425d90).
Report is 1 commits behind head on v1.x.

Additional details and impacted files

@@           Coverage Diff           @@
##             v1.x    #5276   +/-   ##
=======================================
  Coverage   94.66%   94.66%           
=======================================
  Files         322      322           
  Lines        8058     8058           
  Branches     1632     1632           
=======================================
  Hits         7628     7628           
  Misses        430      430           

[chancancode]

my review doesn't really count, but FWIW, I did check that:

1. everything in these two files seems to be updated appropriately, and
2. I didn't see anything in the scripts/*.js referenced here that would need to be updated

[maryliag]

Trying to understand: after next gets merged to main, don't you want to have published on v1 and main? This seems to be replacing to just v1, but how things on main would keep getting published?

[trentm]

Worth having a "1.x" section or note to doc/contributing/releasing.md?

[pichlermarc]

Trying to understand: after next gets merged to main, don't you want to have published on v1 and main? This seems to be replacing to just v1, but how things on main would keep getting published?

@maryliag yes, we want to publish from both:

• backported fixes from v1.x
• 2.x versions starting febuary from main

This workflow gets changed only on the v1.x branch (which is the target for this PR), one can change from which branch the workflow is to be used when triggering it. So when we choose v1.x the PR gets created targeted to v1.x (this change here), but if we choose main we release from main. 🙂

[pichlermarc]

Worth having a "1.x" section or note to doc/contributing/releasing.md?

Good point, updated it here 69675f8 - steps largely remain the same :)

[pichlermarc]

I'll port the docs changes forward to main after merging next back so we have it there as well.

[maryliag]

duh... completely missed this was on v1 branch! My mistake, now makes sense 😄