diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 0000000..d66ffb9 --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,19 @@ +# SPDX-License-Identifier: Apache-2.0 +# Copyright 2026 Junior Deogracias +# +# This file is part of EmbLink Studio, the IDE for EmbLinkRTOS. +# Licensed under the Apache License, Version 2.0; see the LICENSE file at the repository root. +# +# Dependabot: keeps the GitHub Actions used by CI up to date, one grouped pull request a week. +# The core has no runtime dependencies yet; add a pip entry for /core when it gains one. +version: 2 +updates: + - package-ecosystem: github-actions + directory: / + schedule: + interval: weekly + groups: + actions: + patterns: ["*"] + commit-message: + prefix: ci diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 91afba4..caef733 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -90,6 +90,8 @@ jobs: status=0 for c in $(git rev-list --no-merges "${{ github.event.pull_request.base.sha }}..${{ github.event.pull_request.head.sha }}"); do who="$(git show -s --format='%an <%ae>' "$c")" + # Dependabot cannot sign off; its updates are reviewed before they are merged. + case "$who" in "dependabot[bot] <"*) continue ;; esac if ! git show -s --format=%B "$c" | grep -qF "Signed-off-by: $who"; then echo "::error::commit $c has no 'Signed-off-by: $who'" status=1 diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..0b150fa --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,36 @@ + +# Security policy + +## Supported versions + +EmbLink Studio has not had a release yet. Security fixes go to the `main` branch; once releases +start, this table will list the versions that receive them. + +| Version | Supported | +|---|---| +| `main` | Yes | + +## Reporting a vulnerability + +**Do not open a public issue for a security problem.** Report it privately through GitHub: +[Report a vulnerability](https://github.com/EmbLinkOs/EmbLinkStudio/security/advisories/new) +(the *Security* tab, then *Report a vulnerability*). Only the maintainers can see the report. + +Please include: + +- what the problem is and what an attacker could do with it; +- the steps to reproduce it, or a proof of concept; +- the version or commit, and your operating system; +- whether you want to be credited, and under what name. + +## What happens next + +The report is acknowledged within a week. Once the problem is confirmed, a fix is prepared in +a private fork and released together with a GitHub security advisory that credits the reporter, +unless they ask not to be named. Please keep the problem private until the advisory is out. + +## Scope + +In scope: the EmbLink Studio desktop application, EmbLink Studio Core and the protocol between +them. Problems in a third-party component (listed in `third_party/components.json`) are best +reported to that project as well.