[FeatureReq - Partner Center] Roll back to a previous version

[avi12]

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

[ManikanthMSFT]

Hi @avi12,

Thank you for reporting this. We are looking into this and will let you know as soon as we have an update.

[sandeepchads]

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.

[avi12]

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 In this scenario, rolling back to a previous release gives me the proper time to work on a hotfix

[sandeepchads]

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.

[carlosjeurissen]

In an ideal world:

• In every situations one can upload a new binary.
• Only the latest uploaded binary will be needed to be reviewed by the stores team.
• One can choose any of the reviewed binaries to be served to the user as long as it is higher or equal to the highest version already served to the user.
• If an already reviewed binary is chosen with a version lower than the highest already served, a rollback feature would be offered which modifies just the version of said binary.
• A priority review can be requested with a certain budget (say once a year) in the case of a severe security vulnerability.

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.

[sandeepchads]

Acknowledge the feedback @carlosjeurissen

[ManikanthMSFT]

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.

[thryyy]

Hi @ManikanthMSFT, thank you for keeping us updated on this feature request. Since it's been a few months since the last update, I was wondering if you could share an approximate timeline for when this might be implemented?

This would help us better plan our release strategies

[ManikanthMSFT]

Hi @thryyy, thank you for your patience and continued interest in this feature request. At this time, we don’t have an estimated timeline for its implementation. However, please rest assured that as soon as we have an update, we will inform you immediately. We understand how important this is for your release strategies and appreciate your understanding.