Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UINV-529: Bump minimum okapi interfaces for pieces (2.0 3.0) #754

Merged
merged 3 commits into from
Jan 30, 2024

Conversation

alisher-epam
Copy link
Contributor

Purpose

UINV-529 - BREAKING Bump minimum okapi interfaces for pieces (3.0)

Approach

Screenshots

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.

@alisher-epam alisher-epam requested review from a team January 30, 2024 10:31
@alisher-epam alisher-epam self-assigned this Jan 30, 2024
Copy link

github-actions bot commented Jan 30, 2024

Jest Unit Test Statistics

    1 files  ±0  113 suites  ±0   4m 56s ⏱️ +15s
350 tests ±0  350 ✔️ ±0  0 💤 ±0  0 ±0 
354 runs  ±0  354 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit 9c41f18. ± Comparison against base commit 7b46f8e.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Jan 30, 2024

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit 9c41f18. ± Comparison against base commit 7b46f8e.

♻️ This comment has been updated with latest results.

@alisher-epam alisher-epam changed the title UINV-529: *BREAKING* Bump minimum okapi interfaces for pieces (3.0) UINV-529: Bump minimum okapi interfaces for pieces (2.0 3.0) Jan 30, 2024
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@NikitaSedyx NikitaSedyx merged commit 796fdcd into master Jan 30, 2024
6 checks passed
@NikitaSedyx NikitaSedyx deleted the UINV-529 branch January 30, 2024 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants