-
Notifications
You must be signed in to change notification settings - Fork 975
Unhide bitwarden password manager #7921
Comments
Can we unhide now that #7830 is closed? |
@kspearrin absolutely- we'll need a new version of Muon. I'll set a milestone for the release after the current one. If you'd like, you could submit a revert of the above as a PR 😄 |
@bsclifton Done. #8776 |
Unhide bitwarden password manager. resolves #7921
@bsclifton Just trying to get an idea here. We'd like to prepare some announcement material to inform our users. What version of brave is slated to have bitwarden available in it? |
@kspearrin comment left here: Basically, it's in our 0.17.x releases. Here's a link to the latest, if you wanted to test it out 😄 We should be able to ship within 1-2 weeks 😄 |
@bsclifton How do extension updates work in brave? I'm testing with 0.17.1 and am getting a very outdated version of bitwarden (1.10.0) that is full of issues because it's using server APIs that are not backwards compat anymore. |
@kspearrin right now, it's a manual process we have to run (I'm looking at automating the update process). I should be able to safely bump bitwarden without an issue. Hang tight... |
@bsclifton Ok, no worries. We do have a somewhat critical update coming out today or tomorrow that I would like to ensure brave gets updated to before the release. |
@bsclifton Issue created #9479 |
@kspearrin I'm about to take a closer look at this issue. Aiming to resolve asap, and ship. |
@jonathansampson ok. Please let me know if/when there is a branch I can look at/test. Also, we just pushed a new version, 1.14.2 , to the chrome store today. It would be nice if that update made it in as well since I know auto updates is a missing feature at the moment. |
@kspearrin good call- we do need to unhide it. This issue was closed prematurely when a different commit / issue was resolved. I'll re-open and unhide it shortly |
…he expected chrome API" This reverts commit a79effc. cc: @kspearrin, @jonathansampson, @luixxiul Fixes #7921
Issue is now resolved after committing 2c2e19a 😄 |
@kspearrin you can try it out using the |
@bsclifton I will wait for the new dev build. |
Tentatively moving to 0.19.x - we've got it disabled for now because of issues we ran into. We'll continue working away at those and plan to release with 0.19.x |
Let's track this with #4776 instead |
Test plan
#8829 (comment)
#6918 (comment)
Once #7830 is supported, we can revert 0744193
#7919 #4776
The text was updated successfully, but these errors were encountered: