FINERACT-2421: Add Verify Liquibase Backward Compatibility check

[adamsaghy]

Description

Describe the changes made and why they were made. (Ignore if these details are present on the associated Apache Fineract JIRA ticket.)

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made.
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[Aman-Mittal]

Seems Ok just asking if i run this check in forked branch on push event which develop branch will it checkout? That forks develop eg. forkedRepo/develop or only apache/develop?

[adamsaghy]

I believe it takes the origin which would be "apache", but i can double check.

[Aman-Mittal]

https://github.com/Aman-Mittal/fineract/actions/runs/20916627097/job/60091598962?pr=4

Im running this workflow in my forked repo to crosscheck, will confirm you with results. what it is doing.

[Aman-Mittal]

just crosschecked

• /usr/bin/git -c protocol.version=2 fetch --prune --no-recurse-submodules origin +refs/heads/:refs/remotes/origin/ +refs/tags/:refs/tags/
  From https://github.com/Aman-Mittal/fineract
  • [new branch] FINERACT-2326/Refactor-some-logical-codes -> origin/FINERACT-2326/Refactor-some-logical-codes
  • [new branch] FINERACT-2326/depricated-code-and-optimizations -> origin/FINERACT-2326/depricated-code-and-optimizations
  • [new branch] FINERACT-2346/Refactor-maintainability-issue -> origin/FINERACT-2346/Refactor-maintainability-issue
  • [new branch] FINERACT-2346/sonarqube-fixes -> origin/FINERACT-2346/sonarqube-fixes
  • [new branch] FINERACT-2402/kafka-docker-update -> origin/FINERACT-2402/kafka-docker-update
  • [new branch] FINERACT-2402/kafka-server-env-changes -> origin/FINERACT-2402/kafka-server-env-changes
  • [new branch] FINERACT-2421/antMatcher-deprecation -> origin/FINERACT-2421/antMatcher-deprecation
  • [new branch] FINERACT-2421/maintainabilility-refractor-phase-3 -> origin/FINERACT-2421/maintainabilility-refractor-phase-3
  • [new branch] FINERACT-2421/maintainability-refractor-phase-4 -> origin/FINERACT-2421/maintainability-refractor-phase-4
  • [new branch] FINERACT-2421/maintainability-refractor-phase-5 -> origin/FINERACT-2421/maintainability-refractor-phase-5
  • [new branch] FINERACT-2421/verify-liquibase-compability -> origin/FINERACT-2421/verify-liquibase-compability

When we create PR- it checks the forked branch repo, based on to where PR is trying to merge when i raised the pr against my forked develop it checked out to my forked develop branch

https://github.com/Aman-Mittal/fineract/actions/runs/20916627097/job/60091598962?pr=4

[Aman-Mittal]

I think this is ok to merge. Behaviour is based on where the GA is ran. For anyone who wants to tests this new GA check i think we should add this on md file. where forked develop must be synced with upstream develop.

[adamsaghy]

No, I think it would be safer to use the PR base repo and ref here... let me rework.

[meonkeys]

see also: #5264