fix: rename panels#393
Closed
elhb wants to merge 6 commits into
Closed
Conversation
johandahlberg
approved these changes
Jun 12, 2026
Contributor
Author
|
To not mess up history I'm renaming the prerelease panels here instead #394 |
Contributor
Author
|
To not mess up history I'm renaming the proximoe-v2 panels here instead #395 |
Contributor
Author
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
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.
Description
Rename the panel files to properly reflect released version names and prerelease version.
Renaming, never released v2.0 to prerelease:
Renaming, first released version to v2.0:
Note: that these two operations confuse the git history a bit,
the history incorrectly looks like:
Fixes: PNA-2956
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce it when relevant.
PR checklist:
pyproject.tomland cited it properly