-
Notifications
You must be signed in to change notification settings - Fork 125
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
[FeatureReq - Partner Center] Roll back to a previous version #159
Comments
Hi @avi12, Thank you for reporting this. We are looking into this and will let you know as soon as we have an update. |
hi @avi12 ack your request. I am just curious, that how has the lack of this feature impacted you? Any real life scenarios would help me a lot to understand how should I prioritize this feature against other items on our backlog. |
Suppose I had been working on a new feature and after finishing, I pushed the update, it successfully passed the review, but then I discovered a bug that could potentially break either the extension or that feature |
Ack the request. I or someone from my team will update this thread when we take up rollback to the previous version on our backlog. |
In an ideal world:
This would greatly improve the response time and reduced vulnerability in case of severe bugs and security vulnerabilities and help keep users secure and happy. |
Acknowledge the feedback @carlosjeurissen |
Hey @avi12, @carlosjeurissen, we wanted to inform you that the feature you inquired about is currently on our backlog. We will update you once we begin working on this feature. We appreciate your understanding and patience. |
Is your feature request related to a problem? Please describe.
Sometimes a version is accidentally pushed and it's good to have such a safety net of rolling back to a previous version
Chrome Web Store lets roll back to the immediate previous version
Firefox Addons lets roll back to any previous version
Describe the solution you'd like
Have a UI that lets the dev select a version to roll back to
The text was updated successfully, but these errors were encountered: