TLS warning fires on Pi-Bolt builds that already have the October 2026 fixes (Bun 1.4.3 with oven-sh/bun#46300)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- backend
Research direction
Start with runtime-tls.ts and read runtimeTlsWarning() to see how the Bun version check triggers the warning. The issue suggests checking the TLS fix itself using CERT_REVOKED behavior or tls.rootCertificates.length; confirm how the existing tests cover this warning. Done means Pi-Bolt 1.0.9 and later do not show the warning while affected Bun versions still do.
Written by the indexing model from the issue text.
Description
runtimeTlsWarning() in runtime-tls.ts warns whenever process.versions.bun is below 1.4.4. Pi-Bolt 1.0.9 and later run Bun 1.4.3 with oven-sh/bun#46300 ported (blocked keys, NSS 3.131.1 roots), and will keep reporting 1.4.3 (opensec-git/Pi-Bolt#228). So every Pi-Bolt start shows "this Pi build runs on Bun v1.4.3, which is missing the October 2026 TLS fixes", on a build that has them.
The Pi-Bolt maintainer's suggestion in #228 is to check for the fix itself rather than the version: a chain with a blocked key fails with CERT_REVOKED, or tls.rootCertificates.length is 118.
Environment: @plannotator/pi-extension 0.28.52, Pi-Bolt 1.1.4 (Pi 1.5.0), Linux x64.
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 649
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 862
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from backnotprop/plannotator
-
[Feature Request] shortcut for "send with a note"Possibly taken @ilyaZar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
backnotprop/plannotator#2912 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
backnotprop/plannotator#2643 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
backnotprop/plannotator#2243 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
Annotate documentation omits per-file version history and privacy controlsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
backnotprop/plannotator#1086 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
backnotprop/plannotator#2898 ·
Maintainers usually reply within 1 day
All issues in backnotprop/plannotator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-containers#655 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dsh-tauri-desk/deepseek-harness-desktop#1477 · 1 comment ·
-
[docs] RELEASE.md: wrong branch name, no check that the prepare PR merged with the right subject, manual publish stepPossibly taken @albertteoh claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jaegertracing/jaeger-ui#4739 ·
Maintainers usually reply within 1 day