Merge lp://staging/~abreu-alexandre/webapps-core/email-clear-cache-once-on-update into lp://staging/webapps-core
Proposed by
Alexandre Abreu
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Alberto Mardegan | ||||
Approved revision: | 124 | ||||
Merged at revision: | 125 | ||||
Proposed branch: | lp://staging/~abreu-alexandre/webapps-core/email-clear-cache-once-on-update | ||||
Merge into: | lp://staging/webapps-core | ||||
Diff against target: |
28 lines (+4/-2) 2 files modified
webapp-gmail/manifest.json (+3/-2) webapp-gmail/webapp-click.hook (+1/-0) |
||||
To merge this branch: | bzr merge lp://staging/~abreu-alexandre/webapps-core/email-clear-cache-once-on-update | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alberto Mardegan (community) | Approve | ||
Review via email: mp+279513@code.staging.launchpad.net |
Commit message
Force cache deletion on update to mitigate for potential issues created by its content & saml requests for some accounts
Description of the change
Force cache deletion on update to mitigate for potential issues created by its content & saml requests for some accounts.
This change relies on:
https:/
To post a comment you must log in.
LGTM, but is this really happening on update? Shouldn't we have an "update" key in the manifest (I guess we can add it already, even if your other MP is not merged yet)?