Burrow v0.1.3

Burrow v0.1.3

This release reduces repeated CI work and simplifies user management actions.
Linux amd64 and arm64 containers and standalone binaries remain supported.

Changes

• Main push CI reuses successful PR regression only when the recorded tested
  Git tree matches the merged commit exactly. Missing, expired or invalid
  evidence causes full regression. PR, dev and manual runs retain full tests.
• Main still builds both native architecture images, tests their production
  PostgreSQL startup and publishes the tested images to GHCR and Docker Hub.
• Release metadata no longer invalidates dependency build layers. The pinned
  image publisher is cached, tested image artifacts are kept for seven days,
  and browser tests against packaged binaries avoid rebuilding the frontend.
  Both release architectures retain their packaged-binary SQLite/MFA/OIDC
  browser suite and production PostgreSQL container smoke tests.
• Users password reset uses a lock icon; MFA reset uses a shield icon. Both
  retain translated tooltips and accessible labels.
• Remove the standalone Revoke sessions button and its management API
  (POST /api/v1/users/{id}/revoke-sessions). Integrations using that endpoint
  must stop calling it. Password reset, MFA reset, logout and account changes
  retain their existing session invalidation behavior.

Install

Docker selects the appropriate Linux architecture from either image:

ghcr.io/arkgravity/burrow:v0.1.3
docker.io/logic3579/burrow:v0.1.3

The six attachments are:

• burrow_v0.1.3_linux_amd64.tar.gz
• burrow_v0.1.3_linux_arm64.tar.gz
• burrow_v0.1.3_deploy.tar.gz
• INSTALL.md
• IMAGES.txt
• SHA256SUMS

Both binaries embed the frontend and require glibc 2.36 or newer, such as
Debian 12. Follow the attached installation guide and verify the attachment
checksums.

Upgrade and MFA policy

Back up the database, original master key and configuration before upgrading.
Select the v0.1.3 image or binary, run migration and seed, then start the server.
There is no new database migration; schema v5, identities, passwords, grants,
applications and signing keys are preserved.

The global MFA policy is unchanged from v0.1.2: security.mfa_enabled and
BURROW_MFA_ENABLED default to false. Keep your existing policy setting.
When upgrading from v0.1.0 or v0.1.1, explicitly set BURROW_MFA_ENABLED=true
or security.mfa_enabled: true before startup to retain mandatory MFA.
Native commands do not load .env; exported environment values override YAML.

Verification scope

Release preparation requires successful main push CI for the exact tagged
commit, including its trusted PR regression record or full regression, both
image smoke tests and image publication. Both native release jobs must pass
the packaged-binary browser suite and production PostgreSQL startup checks
before the draft can be published. See Actions for this version's results.

The maintainer accepted the CI/release optimization and Users action changes.
That user-reported acceptance is separate from automated checks, downstream
SSO testing, production validation and OpenID Foundation certification.

中文说明

v0.1.3 优化 CI/release，并简化 Users 用户管理操作。

main 合并后的 push 仅在已成功 PR 的测试 Git tree 与合并提交完全一致时复用完整
回归结果；证据缺失、过期或无效时自动执行完整回归。PR、dev 和手动运行仍执行
完整测试。main 继续构建 amd64/arm64 镜像，验证 PostgreSQL 生产启动并推送双仓库。
发布流程改进构建缓存、缓存固定版本的镜像发布工具、将测试镜像保留七天，使用
已打包二进制运行浏览器测试时不再重复构建前端。两个架构的正式包浏览器回归和
PostgreSQL 容器烟测仍为发布前置条件。

Users 的重置密码改用锁图标，重置 MFA 改用盾牌图标，保留中英文提示和无障碍标签。
移除独立 Revoke sessions 按钮及 POST /api/v1/users/{id}/revoke-sessions API；
使用该接口的集成需停止调用。密码重置、MFA 重置、退出和账户变更仍保留原有的
会话失效处理。

继续提供双架构二进制、统一双架构镜像、共享部署包、安装指南、摘要和校验文件。
升级前备份数据库、原主密钥和配置，依次执行迁移、seed、启动；schema v5 不变。
MFA 开关仍默认关闭，从 v0.1.2 升级保留现有设置；从 v0.1.0/v0.1.1 升级且需要
继续强制 MFA 时，必须在启动前显式设置 BURROW_MFA_ENABLED=true 或 YAML 的
security.mfa_enabled: true。

用户已验收本次需求；人工验收与自动化结果、下游 SSO、生产部署和官方认证分别记录。

Burrow v0.1.2

Burrow v0.1.2

This release makes the global MFA policy configurable, simplifies login/logout
presentation and improves password validation feedback. Linux amd64 and arm64
containers and standalone binaries remain supported.

Changes

• security.mfa_enabled in YAML and BURROW_MFA_ENABLED in the environment
  enable or disable TOTP for every account, including Administrator. Both
  defaults are false; manually enable MFA when it is required.
• Disabling MFA preserves existing encrypted bindings. Temporary passwords
  still require a change. Re-enabling MFA rejects password-only sessions and
  requires login with authenticator setup or verification. OIDC amr reports
  the authentication actually completed.
• The login brand no longer ends with a slash. The signed-in logout button
  revokes the Burrow session immediately and returns to login. Application-initiated
  OIDC logout retains its confirmation and redirect checks.
• User creation explains password-policy failures and validates the backend's
  12–256 UTF-8 byte limit before submission. Password reset and change use the
  same validation, with English and Simplified Chinese messages.
• Updated product screenshots from the maintainer's local browser acceptance,
  plus Grafana and Nightingale application icon examples.
• GHCR and Docker Hub publish unified multi-platform tags from tested images
  by digest, without architecture-suffixed tags.

Install

Docker selects the appropriate Linux architecture from either image:

ghcr.io/arkgravity/burrow:v0.1.2
docker.io/logic3579/burrow:v0.1.2

The six attachments are:

• burrow_v0.1.2_linux_amd64.tar.gz
• burrow_v0.1.2_linux_arm64.tar.gz
• burrow_v0.1.2_deploy.tar.gz
• INSTALL.md
• IMAGES.txt
• SHA256SUMS

Both binaries embed the frontend and require glibc 2.36 or newer, such as
Debian 12. Containers are the recommended deployment method. Follow the attached
installation guide and verify the attachment checksums.

Upgrade and MFA policy

Back up the database, original master key and configuration before upgrading.
Select the v0.1.2 image or binary, run migration and seed, then start the server.
There is no new database migration; schema v5, identities, passwords, grants,
applications and signing keys are preserved.

v0.1.0 and v0.1.1 required MFA. v0.1.2 defaults to disabling it. To preserve
mandatory MFA when upgrading, set BURROW_MFA_ENABLED=true in your Compose
.env or exported service environment before starting the new version.
For native commands, you can instead set the selected YAML configuration:

security:
  mfa_enabled: true

Native commands do not load .env. Environment values override YAML. Restart
the service or recreate the Compose application container after changing this
setting. Existing bindings are retained whichever policy you select.

Verification scope

The release workflow requires successful full CI for the exact main commit.
Both native release jobs must pass the packaged-binary SQLite/MFA/OIDC browser
suite and production PostgreSQL container startup checks before a draft is
published. See Actions for the results of this version.

The maintainer reported successful local browser acceptance of administrator
application, role, group and user creation, followed by new-user login and the
application portal. That checkpoint is separate from automated CI, downstream
SSO login, production validation and OpenID Foundation certification.

中文说明

v0.1.2 新增全局 MFA 开关，security.mfa_enabled 和 BURROW_MFA_ENABLED
默认均为 false，需要 TOTP 时必须手动开启，开启后作用于所有账户（含管理员）。
关闭时保留已有绑定，临时密码仍需修改；重新开启后，密码登录产生的会话需重新登录
并完成绑定或验证。OIDC amr 按实际完成的认证返回。

登录页品牌后的斜杠已移除，站内退出改为单击立即注销；应用发起的 OIDC 退出仍保留
确认及重定向校验。创建用户、重置密码和改密表单统一校验 12–256 UTF-8 字节长度，
密码策略失败时给出明确的中英文提示。README 更新本地人工验收截图，SSO 示例补充
Grafana 和 Nightingale 的图标 URL。

继续提供 Linux amd64/arm64 二进制和统一双架构镜像标签，不发布架构后缀标签。
附件包含两个二进制包、共享部署包、安装指南、镜像摘要和校验文件。

从强制 MFA 的 v0.1.0/v0.1.1 升级时，若要继续要求 MFA，务必在启动新版前
显式设置 BURROW_MFA_ENABLED=true，或在所选 YAML 中设置 security.mfa_enabled: true。
升级前备份数据库、原主密钥和配置，依次执行迁移、seed、启动；schema v5 保持不变。
用户报告的本地管理功能及新用户登录/门户验收，与自动化检查、下游应用 SSO、
生产部署和官方 OIDC 认证分别记录。

Burrow v0.1.1

Burrow v0.1.1

This release adds native Linux amd64 and arm64 builds for Burrow's container
images and standalone binaries. The authentication, authorization and database
schema remain the same as v0.1.0.

Changes

• Native amd64 and arm64 CI coverage for SQLite/PostgreSQL race tests,
  Chromium/MFA/OIDC browser flows and container builds.
• Both architectures under the same versioned image tag in GHCR and Docker Hub.
• Separate amd64 and arm64 binary archives, each extracted from its tested
  release image and verified through the packaged-binary browser suite.
• A shared Compose deployment archive, version-specific installation guide,
  platform/index image digests and complete attachment checksums.
• Publication reuses the saved images and checks architecture, commit, exact
  index membership, public index access and matching digests across registries.

Install

Docker automatically selects Linux amd64 or arm64 from either image:

ghcr.io/arkgravity/burrow:v0.1.1
docker.io/logic3579/burrow:v0.1.1

The six attachments are:

• burrow_v0.1.1_linux_amd64.tar.gz
• burrow_v0.1.1_linux_arm64.tar.gz
• burrow_v0.1.1_deploy.tar.gz
• INSTALL.md
• IMAGES.txt
• SHA256SUMS

Both binaries embed the frontend and require glibc 2.36 or newer, for example
Debian 12. Containers are the recommended deployment method. Follow the attached
installation guide for credentials, TLS, configuration and startup order.

Upgrade and verification

Back up the database, original master key and configuration before upgrading.
Select the v0.1.1 image or matching binary, then run migration and seed before
starting the server. This release introduces no new database migration; it keeps
schema v5 and mandatory TOTP. The published v0.1.0 artifacts remain unchanged.

The release workflow requires successful full CI for the exact main-branch
commit. Both native preparation jobs must pass packaged-binary browser tests
and production-mode PostgreSQL container startup checks before publication.
Results are available under the repository's Actions tab. These engineering
checks do not constitute OpenID Foundation certification or validation of your
production deployment.

中文说明

v0.1.1 新增 Linux amd64 和 arm64 双架构镜像与独立二进制。
GHCR 和 Docker Hub 共用 v0.1.1 标签，Docker 根据宿主架构自动选择镜像。
两个二进制归档均内嵌前端，要求 glibc 2.36 或更新版本；推荐通过容器部署。

CI 在两个原生架构上执行双数据库 race、浏览器和镜像构建检查。
Release 从各自镜像提取并打包二进制，测试打包后的程序及生产模式 PostgreSQL 容器，
随后复用已测试镜像发布；附件包含两个二进制包、共享部署包、安装指南、镜像 digest 和校验文件。

本次不修改认证、权限与数据库结构，继续使用 schema v5 和全员强制 TOTP。
从 v0.1.0 升级前请备份数据库、原 master key 和配置，依次执行迁移、seed 和启动。
旧 v0.1.0 发布产物保持原样。自动化工程检查不代表官方 OIDC 认证或生产环境验证。

Burrow v0.1.0

Burrow v0.1.0

Burrow's first release is a lightweight, single-organization OpenID Connect
identity provider. The Go backend and React interface ship together. Licensed
under MIT. This is an early release; future configuration, API and database
changes may require migration.

Features

• Shared SSO with Burrow passwords and mandatory TOTP for every user.
• Temporary-password changes, first-login authenticator binding, administrator
  MFA reset and operator recovery.
• Users, groups, custom roles, permissions, personal profiles and application
  portals, with transactional authorization and auditing.
• Authorization Code with PKCE S256; confidential Web and public SPA clients.
  Administrators may enable an explicit no-PKCE exception for an individual Web
  application; SPA clients always require PKCE.
• Persistent signing keys, key rotation, exact callback/origin matching and
  revalidation of access at authorization and code exchange.
• English and Simplified Chinese, with light, dark and system themes.
• PostgreSQL production storage; SQLite development and test storage.

Install

Linux amd64 container images:

ghcr.io/arkgravity/burrow:v0.1.0
docker.io/logic3579/burrow:v0.1.0

Attachments include the Linux amd64 binary with embedded UI (glibc 2.36+), a
Compose deployment archive, INSTALL.md, IMAGES.txt with registry digests and
SHA256SUMS. Containers are the recommended deployment method. See the attached
installation guide for credentials, TLS, configuration and startup order.

Upgrading development versions

Back up the database and preserve its original master key. Run migration and
seed before starting the server. Schema v5 revokes old Burrow sessions/tokens
and unfinished authorizations; users sign in again and bind TOTP. Accounts,
passwords, grants, application configuration and signing keys are preserved.
Older Provider-based databases must first satisfy the password-only migration
requirements. Rollback requires a compatible database backup, configuration and
master key; replacing the image alone does not reverse migrations.

Scope and verification

The release workflow requires successful full CI for the exact main-branch
commit, then runs browser regression tests against the packaged binary and
production-mode PostgreSQL startup checks against the release container.
Workflow results are available under the repository's Actions tab.

The user reported local Grafana, Nightingale and Harbor web-login acceptance on
2026-10-01, and MFA browser acceptance on 2026-10-02. These are historical user
checkpoints, separate from this release's automated checks and production
validation. The local integration environment has since been removed.

Refresh Tokens, upstream identity providers, external account linking, machine
clients, dynamic registration and cross-application logout are outside this
release. Downstream applications own their sessions. Burrow has not claimed
OpenID Foundation certification.

---

中文说明

Burrow 首个版本提供单组织 OIDC 身份服务：密码与全员强制 TOTP、共享 SSO、
用户/组/角色/权限管理、个人资料及应用门户。支持 Web/SPA 授权码流程，默认要求
PKCE S256；提供中英双语及浅色、深色、系统主题，采用 MIT 许可证。

推荐使用 Linux amd64 容器部署；独立二进制要求 glibc 2.36 或更新版本。
附件包含部署包、安装说明、镜像 digest 和 SHA256 校验文件。生产使用 PostgreSQL、
独立密钥与初始管理员密码，并配置 HTTPS。首次登录需修改临时密码并绑定认证器。

旧开发版升级前请备份数据库并保留原 master key；迁移到 schema v5 会使旧 Burrow
会话与 Token 失效，用户重新登录后绑定 MFA。回滚需要兼容的数据库备份，不能仅
退回旧镜像。早期版本的配置、API 和数据库可能继续演进。工程互通及人工验收记录
不代表官方 OIDC 认证或生产验证。