indah 0.0.1__tar.gz

indah-0.0.1/.githooks/pre-push

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+# Fast pre-push gate: mirrors the cheap CI jobs (lint + fast tests).
+# Bypass once with:  git push --no-verify
+set -euo pipefail
+
+echo "pre-push: ruff check + format check + fast tests"
+uv run ruff check .
+uv run ruff format --check .
+uv run pytest -m "unit or integration" -q
+echo "pre-push: ok"

indah-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,63 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# Cancel superseded runs on the same ref (principle 7).
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - run: uv sync --frozen --extra dev
+      - name: Ruff lint
+        run: uv run ruff check .
+      - name: Ruff format check
+        run: uv run ruff format --check .
+
+  # Fast layer: unit + integration. No external infra, so it runs everywhere
+  # and mirrors the pre-push hook (principles 1, 6).
+  fast-tests:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync --frozen --extra dev
+      - name: Unit + integration tests
+        run: uv run pytest -m "unit or integration" -q
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - name: Build wheel and sdist
+        run: uv build
+      - name: Verify metadata
+        run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  # Heavy layer (browser / real launched app) is added with Slice 1, when
+  # there is a stack to boot. Tracked in SLICES.md V1. Placeholder job keeps
+  # the required-check name stable once branch protection is on.

indah-0.0.1/.github/workflows/publish.yml

@@ -0,0 +1,36 @@
+name: Publish to PyPI
+
+# Publishes on a GitHub Release. Uses PyPI Trusted Publishing (OIDC), so no
+# API token is stored in the repo. One-time setup is documented in
+# docs/RELEASING.md.
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+      - run: uv build
+      - run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # required for trusted publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

indah-0.0.1/.gitignore

@@ -0,0 +1,29 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+
+# Tooling
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+htmlcov/
+
+# Env / secrets
+.env
+.pypirc
+
+# OS / editor
+.DS_Store
+*.swp
+.idea/
+.vscode/
+
+# Frontend build (node is build-time only; keep it out of the repo root)
+node_modules/

indah-0.0.1/AGENTS.md

@@ -0,0 +1,43 @@
+# AGENTS.md
+
+## What
+
+indah is a Python UI framework for ephemeral cloud notebooks (Colab, Runpod):
+reactive, single-port, no Node required at install or runtime.
+
+Status: early planning. `0.0.1` is a name-reservation placeholder; there is no
+working framework code yet. Trust the code over any doc where they disagree, and
+fix the doc.
+
+Layout:
+
+- `src/indah/` package (src layout, hatchling build)
+- `tests/unit`, `tests/integration` (fast layer, no infra), `tests/e2e` (heavy)
+- `docs/` PLAN, SLICES, QUESTIONS, RELEASING, and `docs/adr/` for decisions
+  (the user-facing docs site will be Zensical, FastAPI-style; see ADR-0007)
+- `.github/workflows/` CI and PyPI publish
+
+## Why
+
+Streamlit reruns the whole script per interaction; Gradio is layout-rigid; Reflex
+needs a Node build step that fails inside transient cloud containers. indah fills
+that gap. The load-bearing decisions are in `docs/adr/` (read 0002 on transport
+and 0003 on the reactive model before touching those areas).
+
+## How
+
+Toolchain is `uv` (not plain pip/venv). Common commands (see `make help`):
+
+- Setup: `uv sync --extra dev`
+- Fast gate (run before pushing): `make check` (ruff + `pytest -m "unit or integration"`)
+- Full tests: `uv run pytest`
+- Build: `uv build`
+- Install the pre-push hook once: `make hooks`
+
+Conventions:
+
+- Branch per slice off fresh `main`; land via PR with green CI; no direct pushes to `main`.
+- Every bug or flake gets a failing test first, then the fix.
+- Tests are marked `unit` / `integration` / `e2e`; keep infra-free tests out of the `e2e` mark.
+- Never commit secrets or a PyPI token. Releasing is documented in `docs/RELEASING.md`.
+- User-facing text (README, package description, release notes) uses hyphens, not em-dashes.

indah-0.0.1/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

indah-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Jian Lee
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

indah-0.0.1/Makefile

@@ -0,0 +1,40 @@
+.DEFAULT_GOAL := help
+
+.PHONY: help setup hooks fmt lint test test-fast test-e2e build check clean
+
+help: ## Show this help
+	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | \
+		awk 'BEGIN {FS = ":.*?## "}; {printf "  \033[36m%-12s\033[0m %s\n", $$1, $$2}'
+
+setup: ## Install dev dependencies into a local venv
+	uv sync --extra dev
+
+hooks: ## Install the git pre-push hook
+	git config core.hooksPath .githooks
+	@echo "pre-push hook installed (bypass once with: git push --no-verify)"
+
+fmt: ## Auto-format the code
+	uv run ruff format .
+	uv run ruff check --fix .
+
+lint: ## Lint and format-check (no changes)
+	uv run ruff check .
+	uv run ruff format --check .
+
+test-fast: ## Run the fast layer (unit + integration, no infra)
+	uv run pytest -m "unit or integration" -q
+
+test-e2e: ## Run the heavy layer (browser / real launched app)
+	uv run pytest -m e2e -q
+
+test: ## Run the full test suite
+	uv run pytest -q
+
+build: ## Build the wheel and sdist
+	uv build
+
+check: lint test-fast ## The pre-push gate: lint + fast tests
+
+clean: ## Remove build and cache artifacts
+	rm -rf dist build .pytest_cache .ruff_cache
+	find . -type d -name __pycache__ -prune -exec rm -rf {} +

indah-0.0.1/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.5
+Name: indah
+Version: 0.0.1
+Summary: A Python UI framework for ephemeral cloud notebooks (Colab, Runpod). Reactive, single-port, no Node required.
+Project-URL: Homepage, https://github.com/leejianrong/indah
+Project-URL: Repository, https://github.com/leejianrong/indah
+Project-URL: Issues, https://github.com/leejianrong/indah/issues
+Author-email: Jian Lee <leejianrong2@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: colab,framework,gradio,notebook,reactive,runpod,streamlit,ui
+Classifier: Development Status :: 1 - Planning
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: User Interfaces
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# indah
+
+**A Python UI framework for ephemeral cloud notebooks (Colab, Runpod). Reactive,
+single-port, no Node required.**
+
+Build an interactive UI from a single Python file and launch it straight from a
+Colab or Runpod cell. It keeps Streamlit's zero-config, single-port startup, adds
+the async performance of a real full-stack app, and ships its frontend pre-built
+so there is no Node, npm, or bun anywhere at install or runtime.
+
+> **Status: early planning.** `indah` is not usable yet. This repository currently
+> holds the plan and a `0.0.x` placeholder that reserves the name on PyPI. If you
+> want to follow along, start with [`docs/PLAN.md`](docs/PLAN.md).
+
+## Why another one
+
+| Pain | indah's answer |
+|------|----------------|
+| Streamlit reruns the whole script on every interaction | Reactive signals: only the affected components update ([ADR-0003](docs/adr/0003-reactive-signals-model.md)) |
+| Gradio's layout and state model get awkward past a demo | Plain Python components bound to state, custom layouts |
+| Reflex needs a Node build step that breaks in transient containers | Frontend ships pre-built in the wheel; zero runtime Node ([ADR-0004](docs/adr/0004-svelte-prebuilt-shell.md)) |
+| Colab's proxy does not support WebSockets | SSE + HTTP POST transport that passes the proxy ([ADR-0002](docs/adr/0002-sse-plus-post-transport.md)) |
+
+## How it will work
+
+```mermaid
+flowchart LR
+    subgraph Cell["Colab / Runpod cell"]
+        PY["Your Python app<br/>(reactive signals)"]
+    end
+    subgraph ASGI["Single ASGI app, one port"]
+        CORE["Reactive core<br/>signals to JSON patches"]
+        API["/api: SSE + POST"]
+        STATIC["Pre-built Svelte shell<br/>(static assets in the wheel)"]
+    end
+    Browser["Browser via platform proxy"]
+
+    PY --> CORE --> API
+    STATIC -- served over HTTP --> Browser
+    API -- SSE patches --> Browser
+    Browser -- POST events --> API
+```
+
+One port, standard HTTP plus Server-Sent Events, so it works through the network
+proxies of Colab and Runpod without a tunnel or a local JavaScript toolchain.
+
+## Try the placeholder
+
+```bash
+pip install indah        # reserves the name; no framework yet
+python -c "import indah; print(indah.__version__)"
+```
+
+There is no public API yet. The first working slice ("a live pixel through the
+proxy") is described in [`docs/SLICES.md`](docs/SLICES.md).
+
+## Planning and design
+
+| Doc | What |
+|-----|------|
+| [`docs/PLAN.md`](docs/PLAN.md) | Problem, solution, scope, requirements, architecture |
+| [`docs/SLICES.md`](docs/SLICES.md) | Vertical build increments with test plans |
+| [`docs/QUESTIONS.md`](docs/QUESTIONS.md) | Decision register |
+| [`docs/adr/`](docs/adr/) | Architecture Decision Records |
+
+## Development
+
+```bash
+uv sync --extra dev
+make check        # lint + fast tests (the pre-push gate)
+make help         # list all targets
+```
+
+See [`AGENTS.md`](AGENTS.md) for repo conventions and [`docs/RELEASING.md`](docs/RELEASING.md)
+for the release process.
+
+## License
+
+[Apache License 2.0](LICENSE).

indah-0.0.1/README.md

@@ -0,0 +1,79 @@
+# indah
+
+**A Python UI framework for ephemeral cloud notebooks (Colab, Runpod). Reactive,
+single-port, no Node required.**
+
+Build an interactive UI from a single Python file and launch it straight from a
+Colab or Runpod cell. It keeps Streamlit's zero-config, single-port startup, adds
+the async performance of a real full-stack app, and ships its frontend pre-built
+so there is no Node, npm, or bun anywhere at install or runtime.
+
+> **Status: early planning.** `indah` is not usable yet. This repository currently
+> holds the plan and a `0.0.x` placeholder that reserves the name on PyPI. If you
+> want to follow along, start with [`docs/PLAN.md`](docs/PLAN.md).
+
+## Why another one
+
+| Pain | indah's answer |
+|------|----------------|
+| Streamlit reruns the whole script on every interaction | Reactive signals: only the affected components update ([ADR-0003](docs/adr/0003-reactive-signals-model.md)) |
+| Gradio's layout and state model get awkward past a demo | Plain Python components bound to state, custom layouts |
+| Reflex needs a Node build step that breaks in transient containers | Frontend ships pre-built in the wheel; zero runtime Node ([ADR-0004](docs/adr/0004-svelte-prebuilt-shell.md)) |
+| Colab's proxy does not support WebSockets | SSE + HTTP POST transport that passes the proxy ([ADR-0002](docs/adr/0002-sse-plus-post-transport.md)) |
+
+## How it will work
+
+```mermaid
+flowchart LR
+    subgraph Cell["Colab / Runpod cell"]
+        PY["Your Python app<br/>(reactive signals)"]
+    end
+    subgraph ASGI["Single ASGI app, one port"]
+        CORE["Reactive core<br/>signals to JSON patches"]
+        API["/api: SSE + POST"]
+        STATIC["Pre-built Svelte shell<br/>(static assets in the wheel)"]
+    end
+    Browser["Browser via platform proxy"]
+
+    PY --> CORE --> API
+    STATIC -- served over HTTP --> Browser
+    API -- SSE patches --> Browser
+    Browser -- POST events --> API
+```
+
+One port, standard HTTP plus Server-Sent Events, so it works through the network
+proxies of Colab and Runpod without a tunnel or a local JavaScript toolchain.
+
+## Try the placeholder
+
+```bash
+pip install indah        # reserves the name; no framework yet
+python -c "import indah; print(indah.__version__)"
+```
+
+There is no public API yet. The first working slice ("a live pixel through the
+proxy") is described in [`docs/SLICES.md`](docs/SLICES.md).
+
+## Planning and design
+
+| Doc | What |
+|-----|------|
+| [`docs/PLAN.md`](docs/PLAN.md) | Problem, solution, scope, requirements, architecture |
+| [`docs/SLICES.md`](docs/SLICES.md) | Vertical build increments with test plans |
+| [`docs/QUESTIONS.md`](docs/QUESTIONS.md) | Decision register |
+| [`docs/adr/`](docs/adr/) | Architecture Decision Records |
+
+## Development
+
+```bash
+uv sync --extra dev
+make check        # lint + fast tests (the pre-push gate)
+make help         # list all targets
+```
+
+See [`AGENTS.md`](AGENTS.md) for repo conventions and [`docs/RELEASING.md`](docs/RELEASING.md)
+for the release process.
+
+## License
+
+[Apache License 2.0](LICENSE).