simplify upgrade generator #25203
Merged
simplify upgrade generator #25203
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Failures are linked issues tests. Not possible to make them pass. |
DanielFran
approved these changes
Feb 15, 2024
This was referenced Feb 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reimplement and simplify the upgrade process.
jhipster upgradewill now require thereferenceversion to be installed locally and will upgrade to the version upgrade generator belongs to.Options like source version and target version were removed and should be used at jhipster-migrate.
Fixes #24085.
Fixes #25033.
Fixes #25031.
Closes #19779.
Fixes #19554.
Add checks to recommend jhipster-migrate:
Closes #25014.
Closes #24601.
Closes #24180.
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (below reviewers) and adding
skip-cilabel, you can still see CI build result at your branch.