You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,6 +101,17 @@ If you run into any unexpected compiler failures against our supported TypeScrip
101
101
102
102
Additionally, our Typescript types are compatible with the ECMAScript standard for our minimum supported Node version. Currently, our Typescript targets es2023.
103
103
104
+
#### Running in Custom Runtimes
105
+
106
+
We are working on removing Node.js as a dependency of the driver, so that in the future it will be possible to use the driver in non-Node environments.
107
+
This work is currently in progress, and if you're curious, this is [our first runtime adapter commit](https://github.com/mongodb/node-mongodb-native/commit/d2ad07f20903d86334da81222a6df9717f76faaa).
108
+
109
+
Some things to keep in mind if you are using a non-Node runtime:
110
+
111
+
1. Users of Webpack/Vite may need to prevent `crypto` polyfill injection.
112
+
2. Auth mechanism `SCRAM-SHA-1` has a hard dependency on Node.js.
113
+
3. Auth mechanism `SCRAM-SHA-1` is not supported in FIPS mode.
114
+
104
115
## Installation
105
116
106
117
The recommended way to get started using the Node.js driver is by using the `npm` (Node Package Manager) to install the dependency in your project.
Copy file name to clipboardExpand all lines: etc/notes/releasing.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,11 @@ Fixes are usually released in either the next patch version or in the next minor
30
30
31
31
release-please automatically tags release commits with a tag in the format v<major>.<minor>.<patch>. When backporting, first determine the target minor version and create a release branch for it by branching off of the release tag. The release branch should follow the format `v<major>.<minor>.x`. For example, to create a backport of bson's 6.5 release, create a release branch from the v6.5.0 tag with the name v6.5.x.
32
32
33
-
Then, backport the release action to the target release branch. First, create a copy of our current release action (release.yml). Then, change any references to `main` to the target branch. Double check that there isn't any release tooling on main that doesn't exist on the target branch. If there is, make sure this is backported too. Check if the target branch has a release-please config and manifest file. If not, make sure to adopt changes for release-please v4 (see https://github.com/mongodb/js-bson/pull/682 as an example). Backport all of the above changes to the target release branch.
33
+
Then, backport the release action to the target release branch. This should be done as the first PR on the release branch. Use the following instructions to create it.
34
34
35
-
Now, the release-please will work the same as `main`. Any PRs that merge to the release branch trigger the release action and update release-pleases' release PR. Proceed as normal from here.
35
+
First, create a copy of our current release action (release.yml). Then, change any references to `main` to the target branch. Also, add the branch to the list of CodeQL target branches (codeql.yml). Double check that there isn't any release tooling on `main` that doesn't exist on the target branch. If there is, make sure this is backported too. After opening the PR, check the CI to make sure everything works as expected: add backports of CI fixes as needed.
36
+
37
+
Once the release action PR is merged, release-please will work on this branch in the same way as it does on `main`. Any PRs that merge to the release branch trigger the release action and update the release PR that release-please manages. Proceed as normal from here.
0 commit comments