fix bcrypt binary incompatibility

[mtrezza]

closes #6837

[codecov]

Codecov Report

Merging #6891 into master will increase coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6891      +/-   ##
==========================================
+ Coverage   93.73%   93.80%   +0.06%     
==========================================
  Files         169      169              
  Lines       12220    12220              
==========================================
+ Hits        11455    11463       +8     
+ Misses        765      757       -8     

Impacted Files	Coverage Δ
src/Adapters/Storage/Mongo/MongoTransform.js	88.82% <0.00%> (+0.14%)	⬆️
src/Controllers/DatabaseController.js	95.33% <0.00%> (+0.15%)	⬆️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	92.92% <0.00%> (+0.88%)	⬆️
src/ParseServerRESTController.js	98.18% <0.00%> (+1.81%)	⬆️
src/batch.js	91.83% <0.00%> (+2.04%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0a92cb7...567c8f9. Read the comment docs.

[mtrezza]

@dplewis Aren't packages automatically upgraded by the bots on Github? I am surprised this packages was still on an old version.

[dplewis]

I'm not sure it works for optionalDependencies for the bot

[arlanding]

Is this already released? I'm using "parse-server": "^4.3.0" and I'm still having this issue. #6837

[mtrezza]

The fix has not been released yet.

Parse Server 4.3.0 was released on July 19, this PR was merged in September. You can either use the master branch or fork the repository and manually add the fix to release 4.3.0 to deploy Parse Server with this fix included.

[arlanding]

got it. Do you have a release date?

[mtrezza]

Parse Server has no fixed release cycles, but that is something we will look into to provide more transparency and predictably.

However, in case this would be a first for you, it may be beneficial to figure out how to deploy a forked version of Parse Server in which you add that fix. It is quite easy and once you have done it, you never will have to wait for an official release anymore, so it may be worth trying.

[arlanding]

Thanks!! I did what you said and It worked awesome. I'm a forking man now