The sdist is the package's source, not the repository's

Hatchling's default sdist is everything git does not ignore, which packed the
Claude skills, the GitHub configuration, the PyInstaller spec, the device-side
scripts and the developer environment template into an archive whose only job
is to build and test the wheel. An exclude list keeps the package, the tests
and their fixture, the manual and the files a build reads. The build backend
floor is hatchling 1.26, the first to write the PEP 639 licence fields into the
metadata; an older one built a wheel that said nothing about the licence.
Workflow comments that reasoned from a private repo's metered minutes are
reworded for the public one, a skill's usage line stops naming one machine's
venv, and the scheduler's lock file is ignored in the tree rather than only in
one clone's info/exclude.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Fable 5.1 committed 2026-09-12 19:02:02 -04:00
1 parent 8d3f5d8ed3
commit 8b80a88f03
6 files changed
+44 -20

No files matched your search

+4 -1
View File
@@ -4,7 +4,10 @@ Given an emoji on the command line, report its codepoints and how the three widt
authorities measure it (wcwidth, Rich, prompt_toolkit), then classify it and print the
exact action the `add-narrow-emoji` skill should take. Run from the repo root:
d:\\vibe\\MeshTerm\\.venv\\Scripts\\python.exe .claude\\skills\\add-narrow-emoji\\classify.py 👋
$DEV_VENV_PYTHON .claude/skills/add-narrow-emoji/classify.py 👋
(``$DEV_VENV_PYTHON`` is the interpreter named in ``.dev.env``; ``.dev.env.example`` shows
the shape.)
The point is to remove the guesswork the skill's judgement call depends on: a lone wide
codepoint gets an allowlist entry, a flag is already handled by category, and a ZWJ /
+6 -8
View File
@@ -18,7 +18,7 @@ permissions:
contents: read
# A second push while the first is still running makes the first answer obsolete.
# Cancel it — on a private repo those are metered minutes spent on a stale commit.
# Cancel it — a run on a stale commit is a queue slot and a wait spent on nothing.
concurrency:
group: ci-${{ github.ref }}
cancel-in-progress: true
@@ -54,13 +54,11 @@ jobs:
# and one red leg cancelling its siblings hides the rest until the next push.
fail-fast: false
matrix:
# Shaped for a *private* repo, where minutes are metered and billed by a
# multiplier: Linux 1x, Windows 2x, macOS 10x. So Linux carries the full
# Python range and the costly runners cover the ends of it, which is where a
# version-dependent break actually shows up.
#
# Once the repo is public, standard runners are unmetered: widen this to every
# OS times every version and stop thinking about it.
# Linux carries the full Python range and the slower-to-schedule runners
# cover the ends of it, which is where a version-dependent break actually
# shows up. It was shaped this way when the repository was private and
# minutes were metered; on a public one they are not, so this can widen to
# every OS times every version whenever the wait for a full run is worth it.
include:
- { os: ubuntu-latest, python: "3.10" }
- { os: ubuntu-latest, python: "3.11" }
+3 -3
View File
@@ -1,8 +1,8 @@
# Puts the downloadable builds on the repository's Releases page.
#
# Nothing here leaves GitHub. While the repository is private the release is private too,
# visible and downloadable only by people who can see the repo. This is *not* the PyPI
# publish — that is `release.yml`, it is a separate act, and it does not run from here.
# Nothing here leaves GitHub: a release is exactly as visible as the repository it sits
# on. This is *not* the PyPI publish — that is `release.yml`, it is a separate act, and it
# does not run from here.
#
# Triggered by pushing a version tag, which is the moment a release exists in git anyway:
#
+7 -7
View File
@@ -14,12 +14,12 @@ on:
# Callable, so the release workflow builds these binaries rather than keeping a second
# copy of the matrix that would drift from this one.
workflow_call:
# Only when the packaging itself changes. Three operating systems is not something to
# spend on every commit while the repository is private and minutes are metered.
# Only when the packaging itself changes. A five-platform build takes the better part
# of half an hour, and a commit that touched nothing it freezes has nothing to learn
# from one; the release build is what proves the binaries.
push:
# `main` only. Without this, every Dependabot branch that touches this file — which
# is every action bump — starts a five-platform build, and three of those legs are
# billed at 2x and 10x.
# is every action bump — starts a five-platform build of its own.
branches: [main]
paths:
- "packaging/**"
@@ -50,9 +50,9 @@ jobs:
# fail, it queues forever and holds the whole run open behind it.)
- { os: macos-15-intel, label: macos-x64, ext: "" }
- { os: ubuntu-22.04, label: linux-x64, ext: "" }
# For the uConsole and other 64-bit ARM handhelds. ARM runners are free on
# public repositories; on a private one this leg may sit unclaimed until the
# repo is public. Drop the line if it blocks you.
# For the uConsole and other 64-bit ARM handhelds. The ARM runners are the
# public-repository ones; a private fork of this file may find the leg sits
# unclaimed, and can drop the line.
- { os: ubuntu-22.04-arm, label: linux-arm64, ext: "" }
steps:
- uses: actions/checkout@v4
+1
View File
@@ -12,6 +12,7 @@ dist/
# planning that names hardware and unshipped ideas.
!.claude/
.claude/settings.local.json
.claude/scheduled_tasks.lock
.claude/plans/
.claude/housekeeping.md
# ...and except the GitHub configuration, which only works where GitHub looks for
+23 -1
View File
@@ -1,5 +1,8 @@
[build-system]
requires = ["hatchling"]
# 1.26 is where hatchling started writing the PEP 639 fields below (`License-Expression`,
# `License-File`) into the metadata; an older one builds a wheel that says nothing about
# the licence at all, silently.
requires = ["hatchling>=1.26"]
build-backend = "hatchling.build"
[project]
@@ -74,6 +77,25 @@ path = "meshterm/__init__.py"
[tool.hatch.build.targets.wheel]
packages = ["meshterm"]
# The sdist is the package's source, not the repository's: what someone needs to build
# and test the wheel. Hatchling's default is everything git does not ignore, which swept
# in the Claude skills, the GitHub configuration, the PyInstaller spec, the device-side
# shell scripts (one of which carries data under another licence) and the developer
# environment template — none of which builds, tests, or documents the package. Kept:
# the package, the tests and their fixture, the manual, and the files a build reads.
[tool.hatch.build.targets.sdist]
exclude = [
"/.claude",
"/.github",
"/.dev.env.example",
"/.git-blame-ignore-revs",
"/.gitattributes",
"/CLAUDE.md",
"/docs/survey-*.md",
"/packaging",
"/scripts",
]
[tool.ruff]
line-length = 100
target-version = "py310"