Release v11.0.9

[Terala-Priyanka]

Purpose

Release v11.0.9

Approach

TODOS and Open Questions

Learning

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

• I've added appropriate record to the CHANGELOG.md
• Does this PR meet or exceed the expected quality standards?
  • Code coverage on new code is 80% or greater
  • Duplications on new code is 3% or less
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
  • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

• What other modules will these changes impact?
• Do JIRAs exist to update the impacted modules?
  • If not, please create them
  • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
  • Do they have all they appropriate links to blocked/related issues?
• Are the JIRAs under active development?
  • If not, contact the project's PO and make sure they're aware of the urgency.
• Do PRs exist for these changes?
  • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[zburke]

LGTM

A strategy I like for picking commits from master onto release branches is cherry-pick -x. -x appends a reference to the original commit at the bottom of the commit message (example). That allows GitHub to link back to the original commit, PR, and author, which is very helpful in the scope of troubleshooting. I have cherry-pick -x in my ~/.gitconfig aliased to px so it's easier to type.

To be clear: the process you have for publishing patch releases is 100% fine. I'm merely sharing an alternative approach that includes more history on the release branch.

[Terala-Priyanka]

LGTM

A strategy I like for picking commits from master onto release branches is cherry-pick -x. -x appends a reference to the original commit at the bottom of the commit message (example). That allows GitHub to link back to the original commit, PR, and author, which is very helpful in the scope of troubleshooting. I have cherry-pick -x in my ~/.gitconfig aliased to px so it's easier to type.

To be clear: the process you have for publishing patch releases is 100% fine. I'm merely sharing an alternative approach that includes more history on the release branch.

Thank you for sharing the alternate approach. I see the benefits and would follow it going forward!