fixup! doc: add minutes for 2026-02-18 meeting

Author: aduh95

meetings/2026-02-18.md

@@ -2,9 +2,9 @@
 
 ## Links
 
-* **Recording**: https://www.youtube.com/watch?v=YBDMQlWFHSM
-* **GitHub Issue**: https://github.com/nodejs/TSC/issues/1822
-* **Minutes**: https://hackmd.io/@openjs-nodejs/r1g2TMo5vbl
+* **Recording**: <https://www.youtube.com/watch?v=YBDMQlWFHSM>
+* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1822>
+* **Minutes**: <https://hackmd.io/@openjs-nodejs/r1g2TMo5vbl>
 
 ## Present
 
@@ -45,49 +45,49 @@
 
 ### Announcements
 
-- HackerOne accounts with signal < 1 cannot send vulnerabilities to Node.js (even with new accounts)
-- We are going to change the release plan for Node.js, we are going to only have  one major release a year, which will become LTS (https://github.com/nodejs/nodejs.org/pull/8631), starting from 27. Starting from 27 all of them will be LTS.
-- Collaborator Summit in London at the Bloomberg office on April 14th and 15th. In-person registration link available: https://github.com/openjs-foundation/summit/issues/474
+* HackerOne accounts with signal < 1 cannot send vulnerabilities to Node.js (even with new accounts)
+* We are going to change the release plan for Node.js, we are going to only have  one major release a year, which will become LTS (<https://github.com/nodejs/nodejs.org/pull/8631>), starting from 27. Starting from 27 all of them will be LTS.
+* Collaborator Summit in London at the Bloomberg office on April 14th and 15th. In-person registration link available: <https://github.com/openjs-foundation/summit/issues/474>
 
 ### Reminders
 
 * Remember to nominate people for the [contributor spotlight](https://github.com/nodejs/node/blob/main/doc/contributing/reconizing-contributors.md#bi-monthly-contributor-spotlight)
 
 ### CPC and Board Meeting Updates
 
-*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.
+\*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.
 
-- No updates right now from the Board.
-- CPC working template.
-- Program Committee meeting for RenderATL room, ping Joe Sepi.
+* No updates right now from the Board.
+* CPC working template.
+* Program Committee meeting for RenderATL room, ping Joe Sepi.
 
 ### nodejs/admin
 
 * Add kxxt and luyahan to riscv platform team [#1042](https://github.com/nodejs/admin/issues/1042)
-  - Matteo: no objctions, invite sent.
+  * Matteo: no objctions, invite sent.
 
 ### nodejs/node
 
 * tools: add ncrypto updater script [#61613](https://github.com/nodejs/node/pull/61613)
-  - Filip: ncrypto was extracted from Node.js to be used in Bun and Workerd. The runtimes that would be contributing are on boringssl, so the updates are not going to be helpful for Node.js. The proposal is that the flow is reversed, the updates would flow from node to ncrypto instead. So far we haven't treated it as a dependency. There are currently no guarantees that updates to ncrypto would run inside Node.js CI right now due to a mismatch of OpenSSL versions.
-  - Matteo: if ncrypto becomes a full dependency, they can build Node.js with the new version to verify everything still works.
-  - Antoine: how are workerd using this?
-  - Filip: We should get James on this
-  - Joyee: if there is enough work done in ncrypto, they can just run the Node.js test suite there. The hard part is to verify the OpenSSL compatibility.
-  - Ruy: there are some community aspects as well, letting people know of this lib so they can test.
-  - Matteo: I'm ok with having it as an external dependency as long as Cloudflare or Anthropic commit to support this long term. 
-  - Filip: all the work that Cloudflare and Anthropic would be of no use for Node.js.
-  - ...
-  - Filip: I recommend the source of truth to be the Node.js repo. 
+  * Filip: ncrypto was extracted from Node.js to be used in Bun and Workerd. The runtimes that would be contributing are on boringssl, so the updates are not going to be helpful for Node.js. The proposal is that the flow is reversed, the updates would flow from node to ncrypto instead. So far we haven't treated it as a dependency. There are currently no guarantees that updates to ncrypto would run inside Node.js CI right now due to a mismatch of OpenSSL versions.
+  * Matteo: if ncrypto becomes a full dependency, they can build Node.js with the new version to verify everything still works.
+  * Antoine: how are workerd using this?
+  * Filip: We should get James on this
+  * Joyee: if there is enough work done in ncrypto, they can just run the Node.js test suite there. The hard part is to verify the OpenSSL compatibility.
+  * Ruy: there are some community aspects as well, letting people know of this lib so they can test.
+  * Matteo: I'm ok with having it as an external dependency as long as Cloudflare or Anthropic commit to support this long term.
+  * Filip: all the work that Cloudflare and Anthropic would be of no use for Node.js.
+  * ...
+  * Filip: I recommend the source of truth to be the Node.js repo.
 * sqlite: mark as release candidate [#61262](https://github.com/nodejs/node/pull/61262)
-  - Antoine: the objection was resolved last week, it can land.
+  * Antoine: the objection was resolved last week, it can land.
 
 ### nodejs/TSC
 
 * Dormant Docker Working Group [#1818](https://github.com/nodejs/TSC/issues/1818)
-  - Matteo: we discussed this in private, updats coming.
+  * Matteo: we discussed this in private, updats coming.
 * Collaborator Summits 2026 [#1800](https://github.com/nodejs/TSC/issues/1800)
-  - Matteo: sign up!
+  * Matteo: sign up!
 * Update charter with communication responsibilities [#1754](https://github.com/nodejs/TSC/pull/1754)
 * Self-serve model for funding Node.js work [#1747](https://github.com/nodejs/TSC/issues/1747)
 * Draft Statement of Work - Test reliability lead [#1629](https://github.com/nodejs/TSC/issues/1629)