💬 hodlinator commented on pull request "Windows bitcoind stall debugging [WIP, NOMERGE, DRAFT]":
(https://github.com/bitcoin/bitcoin/pull/30956#issuecomment-2390985894)
I finally read the documentation for [schedule](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule) a bit more closely and realized it only applies to the master branch, so I'm making the "every 3 hours"-schedule happen on my personal master branch for now.

💬 Cunero commented on pull request "Update ci.yml":
(https://github.com/bitcoin/bitcoin/pull/33287#issuecomment-3247171741)
# Security Policy

## Supported Versions

See our website for versions of Bitcoin Core that are currently supported with
security updates: https://bitcoincore.org/en/lifecycle/#schedule

## Reporting a Vulnerability

To report security issues send an email to security@bitcoincore.org (not for support).

The following keys may be used to communicate sensitive information to developers:

| Name | Fingerprint |
|------|-------------|
| Pieter Wuille | 133E AC17 9436 F14A 5CF1 B794 8
...

📝 amitsingh881024-ctrl opened a pull request: "Create SECURITY.md — Strong Security Policy"
(https://github.com/bitcoin/bitcoin/pull/33800)
# Security Policy

## 🔒 Supported Versions

Please refer to the official lifecycle page to identify supported and actively maintained releases:
- [https://bitcoincore.org/en/lifecycle/#schedule](https://bitcoincore.org/en/lifecycle/#schedule)

Security updates are provided only for the listed maintained versions. Users are **strongly advised to upgrade** to supported versions to receive patches.

---

## 🚨 Reporting a Vulnerability

If you discover a security vulnerability, please
...