-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release v5.1.0 #613
Release v5.1.0 #613
Conversation
The build is failing due to the changes have not been merged yet folio-org/ui-plugin-find-organization#124 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the release date in the changelog before merge
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The PR title is "Release v5.1.0" but the CHANGELOG comment is "5.2.0 (IN PROGRESS)".
- The CHANGELOG comment is "5.2.0 (IN PROGRESS)" but the version in
package.json
is still5.1.0
- There are changes to dependency versions in
package.json
that are unrelated to either publishing a release or bumping the version in preparation for the next release.
You need to resolve the contradictions, and then handle these separate activities in separate PRs. You may find it easiest to close this PR and start over once the version updates are made but it's up to you. Make sure to commit the dependency changes first so they can be included in your 5.1.0
release.
Purpose
https://folio-org.atlassian.net/browse/UIORGS-426
Approach
TODOS and Open Questions
Learning
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
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.