Publish the package and its documentation, and move to the papers organization

Add the Zensical documentation of the Python package (docs/package, built by the docs
workflow), merge the standard publish workflow with the setuptools-scm tag check, add the
SPDX header rule to ruff, restructure the README, and point every repository and registry
address at the Gitea organization papers.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B8cL4zN4XpaQF5cBtASzfq
This commit is contained in:
alexmandClaude committed 2026-10-19 04:23:49 -04:00
1 parent bdbf03ebee
commit 30d310f64d
37 files changed
+1005 -83

No files matched your search

+8
View File
@@ -0,0 +1,8 @@
# Changelog
The changelog is one file, `CHANGELOG.md` at the root of the repository, so there is a single copy to keep in sync.
It is published with the format documentation at <https://paperspec.scient.ing/CHANGELOG.html>, and the source is at <https://git.scient.ing/papers/paperspec/src/branch/main/CHANGELOG.md>.
Its top-level headings are the versions of the formats, and a release of the Python package that changes only the code is a subsection under the current format version, as `### 0.1.1` sits under `## 0.1.0`.
The package version comes from the git tag; the format version is the one `CHANGELOG.md` and `pixi.toml` state.
When a release is tagged, the publish workflow takes the release notes from the section whose heading contains the version.