chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@accounts/mongo-password@0.32.3

Patch Changes

• #1209 5fa570d4 Thanks @gezquinndesign! - If users are currently using the Node Mongo Driver v4/Mongoose v6 (both are designed for use with MongoDB 5), this patch ensures no errors thrown when using these methods.

• Updated dependencies [c6b79add]:

  • @accounts/types@0.33.2

@accounts/graphql-api@0.33.2

Patch Changes

• #1194 a4fd732d Thanks @zenweasel! - Fix repo links in package.json

• #1203 0a402215 Thanks @mrcleanandfresh! - Added additional examples for how to authenticate with @accounts/graphql-api

@accounts/two-factor@0.32.3

Patch Changes

• #1182 4b6878fb Thanks @pradel! - Add missing await to when unsetting two-factor

• Updated dependencies [c6b79add]:

  • @accounts/types@0.33.2

@accounts/types@0.33.2

Patch Changes

• #1196 c6b79add Thanks @BarbecueSilver! - Add missing extraData property to the Session type.

[gezquinndesign]

HI @pradel , just wondering if I missed something in my PR or if it should have been covered by the release process: now that @accounts/mongo-password is at 0.32.3, when do the packages that have it as a dependency (eg @accounts/mongo) have their dependencies updated to use the new version?

[pradel]

@gezquinndesign as the mongo package is requesting the dependency ^0.32.2, you can tell your package manager to update mongo-password for your project. You can use the new published mongo-password without updating @accounts/mongo in your project :)

[gezquinndesign]

Got it! Just did a yarn upgrade @accounts/mongo and that sorted it. Thanks 🙂