v0.6.3 — 故障升级与乱序保护

This patch preserves immediate severity escalation during an active incident's deduplication window and records older lifecycle events without allowing them to change incident state or create deliveries. Incident identity remains client + route + dedupe_key.

Raw events, event IDs, subscriptions, routes, silence rules and other channels' info/test behavior are retained. There is no database schema migration or added recovery timer. Sources must establish consecutive successful checks before sending resolved; the gateway does not infer health from elapsed time.

Validation: Go tests, go vet, release configuration checks, isolated Docker E2E, website/link checks and the signed example test. GitHub Actions builds linux/amd64 and linux/arm64, validates SBOM/provenance, and publishes directly to the existing ACR registry. Per-platform evidence is retained in the release-evidence-v0.6.3 Actions artifact.

Upgrade by replacing the image after a paired data/secrets backup. Roll back to the previous image while retaining current data. v0.6.2 was superseded before production deployment to correct release references; its workflow was cancelled and its tag was not rewritten.

v0.6.1 — 已有渠道编辑

已有通知渠道现在可以直接点击“编辑”，回填配置后保存，无需重新创建或手动输入已有 ID。保存后立即生效，路由引用保持不变。

• 支持飞书、Telegram、ntfy、SMTP；编辑时固定渠道 ID 与类型，并提供取消编辑。
• 已保存的 URL、Token、签名密钥和 SMTP 密码不回显，留空保留，填写新值可替换；飞书关键词回填，主动清空可移除。
• 正式收录现有生产的 MCP 2.0、可选 alert.created Events 与 EgressHub SDK 源码基线。MCP 固定使用 2026-07-28，不支持旧版 initialize 握手；Events 默认关闭。
• 通知 API、OIDC、单进程 SQLite/Worker 和容器安全边界保持。

验证：Go 全量测试、go vet、release checks、渠道编辑 Docker E2E；admin/mcpapi/runtimecfg race；官方 MCP Client 2.3.1、固定 Schema 与 13 项独立协议检查。GitHub 发布流程生成并验证 AMD64/ARM64 镜像与各平台 SBOM/来源证明。

ACR 是唯一官方镜像源，拉取需要授权登录。SBOM 与来源证明保留在该版本 Actions 的 release-evidence-v0.6.1 产物中（90 天），并有 GitHub attestations。

升级已有候选版时请保留 OIDC/EgressHub overlay、Secret 和数据卷，并检查 overlay 中的 image，不能只改 .env 标签。备份数据库与主密钥后再升级；详情见部署指南。

发布工具修复：支持多个标签指向同一 OCI 构建索引，仍逐项校验摘要、双平台 SBOM 和来源证明；不同构建索引或损坏引用继续拒绝发布。

v0.5.1 — 服务内嵌公开介绍页

公开项目介绍页通过 Go embed 内嵌于服务，Docker 镜像直接提供匿名 GET / 和 HEAD /，不再需要独立静态文件或 Nginx 页面配置。只注册精确根路径，未知路径仍为 404；通知 API、MCP、OAuth/OIDC 和管理员认证保持不变。页面不创建会话、不读取业务数据，内联样式 CSP 哈希自动生成，不放宽全站策略。无新增依赖或数据库迁移。Go/vet/race、静态检查和真实 Docker E2E 已通过。已有独立首页部署应先验证新镜像 loopback 首页，再归档旧根页扩展并平滑重载 Nginx；原认证和接口代理规则保留。

v0.5.0 — Tinyauth OIDC 统一登录

Changes

• Optional administrator OIDC login, tested with Tinyauth. Authorization Code Flow uses RS256 ID Token validation, state, nonce and PKCE S256.
• Administrator authorization is bound to an explicit issuer + subject. Usernames, email addresses and first login do not grant administrator access.
• File-backed compose.oidc.yaml overlay. The base Compose deployment continues to support password login; OIDC may retain a collapsed password fallback.
• Logout clears only the AlertBridge session. Provider access/refresh tokens are not persisted.

Deployment and compatibility

Use the v0.5.0 image and matching base Compose and optional OIDC overlay. Keep the overlay selected for subsequent Compose operations and back up its server-side configuration separately from the database/master-key recovery pair.

Notification APIs, MCP authorization and business data remain compatible. No database migration is required. Administrator OIDC and MCP OAuth are separate flows; do not interchange their clients, callbacks or credentials. Other OIDC providers require validation against the implementation's same-host HTTPS endpoints, RS256, PKCE and Client Secret Basic constraints. The OIDC login button currently has a fixed provider label; see the deployment guide for this limitation.

Deployment, backup and rollback · MCP / Dots · Website and simulated demo

Validation covers Go tests, vet, release configuration, Docker E2E, OIDC rejection cases and race tests. GHCR remains the release authority; the optional ACR mirror copies and verifies the official AMD64/ARM64 runtime digests.

v0.4.2 — MCP 最近告警直查

list_alerts 新增可选 order=asc|desc：最近 10 条使用 order=desc、limit=10，一次调用即可读取。默认正序、原游标和增量 checkpoint 保持兼容；倒序游标绑定方向且不返回增量 checkpoint。按服务接收时间与记录 ID 稳定排序，权限和认证不变。更新了工具 Schema、说明及接入文档。Go/vet/race、分页回归测试和 Docker OAuth E2E 均通过，无数据库迁移。升级后刷新插件工具定义即可，已有 OAuth 授权无需重建。

v0.4.1 — Dots OAuth 回跳修复

修复授权确认页的 Content-Security-Policy：允许跳转到配置的精确 OAuth 回调地址，解决 Chromium 中点击允许访问后无反应的问题。保留 CSRF、PKCE、回调精确匹配和只读权限限制。已完成回归测试、浏览器对照验证、Go/vet/race 和 Docker E2E；GHCR 双架构镜像及 ACR 镜像同步均成功。无数据迁移。升级后刷新授权页或重新发起连接。

AlertBridge v0.4.0

Adds route-scoped read-only MCP queries and Dots OAuth with PKCE using the existing administrator login. Includes rotating refresh tokens, revocation, deployment guidance and end-to-end tests. Existing HMAC and lightweight notification APIs retain their contracts. No additional runtime service is required.

AlertBridge v0.3.1

Baota webhook compatibility hotfix.

• Return HTTP 200 after durable enqueue from POST /api/v1/notifications so Baota custom message channels recognize success.
• Keep POST /api/v1/events on HTTP 202.
• Preserve Bearer authentication, fixed route/severity, rate limiting, persistent queueing, retry, and dead-letter behavior.
• Update OpenAPI, deployment guidance, admin integration guidance, tests, and ADR-009.

Validation: Go tests, vet, release checks, Docker E2E, multi-architecture GHCR build, provenance attestation, and ACR digest mirror.

AlertBridge v0.3.0

轻量接入

• 新增 POST /api/v1/notifications，使用 Authorization: Bearer ... 发送一次性通知。
• 每个轻量令牌由服务端固定来源、路由、严重程度和 info 状态，并使用独立的 1–60 次/分钟限流。
• 令牌只显示一次，SQLite 仅保存 SHA-256 摘要；正文限制为 8 KiB并拒绝未知字段。
• 管理后台支持创建、停用、轮换和删除轻量令牌，接入指南提供宝塔 $title、$msg、$type 配置示例。

兼容性与升级

• 原有 POST /api/v1/events、HMAC、防重放、幂等和 firing/resolved 生命周期保持不变。
• 升级时会自动创建新的 ingress_tokens 表，不需要手工迁移现有业务配置。
• 官方镜像：ghcr.io/xiongwei-git/alertbridge:v0.3.0。ACR 已复制同一 GHCR digest。
• 本次只发布镜像，不自动升级任何服务器。

验证

• go test ./...
• go vet ./...
• go test -race ./internal/auth ./internal/store ./internal/runtimecfg ./internal/httpapi ./internal/admin
• ./test/release/run.sh
• ./test/e2e/run.sh
• GitHub Actions 双架构 GHCR 发布、来源证明和 ACR 镜像复制通过

AlertBridge v0.2.3

部署改进

• 新增可选的国内 ACR 部署镜像，同一正式版本由 GHCR 发布完成后复制，不重复构建。
• compose.yaml 新增 ALERTBRIDGE_IMAGE，默认仍使用官方 GHCR；中国内地服务器可切换到维护者提供的 ACR VPC 镜像。
• ACR 镜像失败不会影响 GHCR 正式发布，版本、SBOM 和来源证明仍以 GHCR 为准。

升级

无数据库迁移。使用 GHCR 的现有部署只需将 ALERTBRIDGE_IMAGE_TAG 改为 v0.2.3。改用 ACR 时还需下载 v0.2.3 的 compose.yaml、登录 ACR，并在 .env 设置 ALERTBRIDGE_IMAGE。

验证

• go test ./...
• go vet ./...
• ./test/release/run.sh
• ./test/e2e/run.sh
• GitHub Actions GHCR 双架构发布及 ACR 镜像复制通过