fix: migrate issue trackers of 2025.26 #1741
Closed
Conversation
This file contains hidden or 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
Starting with version 2025.26 (implemented in commits b345bb4 and 9802ac9 for issue sourcegit-scm#1599) the issue trackers configured in repository settings are stored in a new format, deleting the issue trackers configured before. Since this breaks compatibility, now these issue trackers in the old format used in versions up to 2025.26 are automatically migrated, so they don't get lost. Fixes sourcegit-scm#1725.
|
@love-linger This code is written in a way that it should be easy to revert if the code no longer deems necessary. Maybe in a year, when most people should use versions after 2025.30. |
|
I'm sorry. This PR will not be merged.
|
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.
Starting with version 2025.26 (implemented in commits b345bb4 and 9802ac9 for issue #1599) the issue trackers configured in repository settings are stored in a new format, deleting the issue trackers configured before.
Since this breaks compatibility, now these issue trackers in the old format used in versions up to 2025.26 are automatically migrated, so they don't get lost.
Fixes #1725.