Skip to content
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

Fix/pisco upgrade 2.5 #173

Merged
merged 1 commit into from
Sep 13, 2023
Merged

Fix/pisco upgrade 2.5 #173

merged 1 commit into from
Sep 13, 2023

Conversation

javiersuweijie
Copy link
Member

@javiersuweijie javiersuweijie commented Sep 13, 2023

Due to an incorrect plan name during the 2.4 upgrade, pisco upgrade to 2.5 will fail since the incorrect plan is not registered in this version.

Adding the handler here so that the check will pass.

@javiersuweijie javiersuweijie changed the base branch from release/v2.5 to upgrade/2.5 September 13, 2023 16:47
@codecov
Copy link

codecov bot commented Sep 13, 2023

Codecov Report

Merging #173 (e94e19b) into upgrade/2.5 (35490f9) will decrease coverage by 0.93%.
The diff coverage is 100.00%.

Impacted file tree graph

@@               Coverage Diff               @@
##           upgrade/2.5     #173      +/-   ##
===============================================
- Coverage        69.76%   68.83%   -0.93%     
===============================================
  Files               27       27              
  Lines             1723     1784      +61     
===============================================
+ Hits              1202     1228      +26     
- Misses             407      441      +34     
- Partials           114      115       +1     
Files Changed Coverage Δ
app/app.go 82.36% <100.00%> (+0.10%) ⬆️

... and 2 files with indirect coverage changes

@tuky191 tuky191 merged commit 62e69ac into upgrade/2.5 Sep 13, 2023
9 checks passed
@emidev98 emidev98 deleted the fix/pisco-upgrade-2.5 branch September 14, 2023 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants