UILD-854: Release v2.0.5

[zepheiryan]

Purpose

Prepare v2.0.5 release.

Approach

Cherry pick all commits related to UILD-744, UILD-816, UILD-780

git checkout v2.0.4
git checkout -b b2.0.5
git push origin
git checkout -b tmp-release-2.0.5
git cherry-pick ad070f93ba4c87c6b1749060fa5808b381ef4e9a
git cherry-pick 439e790b89b6b803530457eabdea70dedf6549a8
git cherry-pick c04db0f2b1d6490ed87748734952954f7a084d1d
git cherry-pick d3be01a16a264c7bb2955302d6cfe039a158bc02
git cherry-pick 990237028a4c1d2bb543f61bdc47669a864e27f8
git add CHANGELOG.md
git cherry-pick --continue
git cherry-pick cc7224da287d46ad8daa452dacfcae66ceb3e6b1
git cherry-pick ecdfab5a523ab1a1bf9db3a8366142f3388aafa6
git cherry-pick 569d45a3a5663c0724ac42269640d4b05a52f7fe
git add CHANGELOG.md src/features/edit/hooks/useEditPage.ts
git cherry-pick --continue
git cherry-pick bf9e18b64ee0db9b1940169efa42c53030841edd
git add CHANGELOG.md src/features/
git cherry-pick --continue
git add src/
git cherry-pick --continue
git cherry-pick cc1750498f5a7828ff7d9b0ba0e4be8108565990
git add package-lock.json src/features/edit/hooks/useEditPage.ts
git cherry-pick --continue
git add src/configs/resourceTypes/utils/resourceType.accessors.ts
git cherry-pick --continue
git cherry-pick a5af2d7d6e70fb8706681e929f0e2ab99877ee34
git add src/features/profiles/components/ModalChooseProfile/ModalChooseProfile.tsx
git cherry-pick --continue
git cherry-pick 534549b4a7b928cccc61a8c93d8d257b4945d50c
git cherry-pick fba9ff61e57c05cb0ab24468f9cb88c1133842ac
git add CHANGELOG.md package.json package-lock.json

Refs

https://folio-org.atlassian.net/browse/UILD-854

[github-actions]

Jest Unit Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit dfc4ffb. ± Comparison against base commit a975b9d.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
93.2% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zburke]

A patch release with changes to nearly 400 files is surprising and, frankly, terrifying. Rather than a patch-release-specific branch, I expected the target branch here to be b2.0, where the v2.0.4 release would be the most-recent commit before these cherry-picks.

@zepheiryan, what kind of review are you hoping for on a release commit? Given the original PRs have already been approved, is it necessary to seek approval again?

[zepheiryan]

A patch release with changes to nearly 400 files is surprising and, frankly, terrifying. Rather than a patch-release-specific branch, I expected the target branch here to be b2.0, where the v2.0.4 release would be the most-recent commit before these cherry-picks.

@zepheiryan, what kind of review are you hoping for on a release commit? Given the original PRs have already been approved, is it necessary to seek approval again?

@zburke My prior Citation colleagues were responsible for previous releases, this is the first one I've taken on. Is this part of the process - just before tagging - not usually conditioned on approval (of the prep, not the already-approved code)? The plan from here was to tag the newly merged branch b2.0.5 and then make a GH release as well as a final sync to the changelog on master.

[zburke]

@zepheiryan, yes, I think release-related commits have been handled internal to teams in the past.

There are likely a lot of "because that's how we've always done it" practices, rather than "best" practices, here. I am open to suggestions for improvement.

[zepheiryan]

@zepheiryan, yes, I think release-related commits have been handled internal to teams in the past.

There are likely a lot of "because that's how we've always done it" practices, rather than "best" practices, here. I am open to suggestions for improvement.

@zburke Thanks, I'll close this out and just make the release. I'll take the process as Chesterton's fence for now.