What’s new

What changed in the framework and the CLI, newest first, with the page that explains each change. Releases are tagged on git.splent.io and published on PyPI. Your product takes a release by pinning it under [tool.splent.runtime], which product:build writes.

Table of contents

1. splent_framework
   1. Not released yet
   2. 1.29
   3. 1.28
   4. 1.27
   5. 1.26
   6. 1.25
   7. 1.24
   8. 1.23
   9. 1.22
   10. 1.21
2. splent_cli
   1. Not released yet
   2. 1.49
   3. 1.48
   4. 1.47
   5. 1.46
   6. 1.45
   7. 1.44
   8. 1.43
   9. 1.42
   10. 1.41
   11. 1.40
   12. 1.39
   13. 1.38
   14. 1.37

---

splent_framework

Not released yet

• Storage per feature. Each feature keeps its files in a folder of its own. See Storage.
• HTTP APIs. problem+json errors, cursor pages, ETag and deprecation headers, and accepted() for work that runs later. See HTTP APIs.
• Background tasks report their progress, and run_isolated runs heavy work in a child process with a time and memory limit. See Background tasks.
• A shared rate limit for every feature, and form_guard for public forms. See Rate limits and forms.
• Safe fetching of an address someone else chose, with a total time limit. See Fetching URLs.
• Search fields, facets and sorts one feature adds to another’s. See Search.
• Content helpers such as unique_slug, summary(), page_of() and pager(), and a sitemap built from what features register. See Content helpers.
• The site’s own address and time zone, with site_root(), absolute_url(), site_name() and local_now(). See The site.
• feature_cache, the product’s Redis or each process’s memory. See Cache.
• Every template escapes, and | safe trusts only markup. See Template system.
• Icons, empty states and page behaviours (icon(), empty_state, data-confirm, data-copy, data-reveal) on every shell.
• optional_module and optional_attr, for a feature the product may not have.

1.29

• An editable product’s version is its checkout’s. See The product’s version.
• The framework names what a feature does, not which feature does it, for sessions and task queues. See Framework defaults.

1.28

• A feature’s bundle, drawn from its manifest, with feature_script and feature_style. See A feature’s bundle.
• register_asset takes scope, type and integrity. See register_asset.
• A Content-Security-Policy per page, from the features the page drew. See Content-Security-Policy per page.

1.27

• register_menu_match lights another feature’s menu entry on your screens. See The current entry.
• A list without choices can select a node of the feature model. See Letting a value select features.
• A model of a feature the app does not load cannot break every query. See Database.

1.26

• A key per purpose with SPLENT_DERIVED_KEYS. See Keys per purpose.

1.25

• The audit API, record_event and register_audit_recorder. See Audit and reports.
• report_degraded, request_id and readiness listeners.

1.24

• MARIADB_PORT in every config class. See Environment variables.

1.23

• has_role in every template. See Access control.
• param() reads a runtime value whichever API stored it. See Reading a parameter.
• Protected files are denied by default. See Protected files.
• Tests start on an empty database and keep their files apart. See Fixtures.

1.22

• Typed parameters in [tool.splent.config_schema]. See Typing a setting.

1.21

• A stronger configuration layer wins. See Configuration.
• Background tasks, @task and enqueue. See Background tasks.
• Health probes, /healthz and /readyz. See Health probes.
• SameSite from the environment. See SameSite.
• The site menu section. See Menus and shells.

---

splent_cli

Not released yet

• SQL and XSS sinks. A command reads a feature’s sources for them, product:validate checks them in an eighth phase, and feature:release refuses a feature that has one.
• The product’s storage in one volume, migrated at start.
• feature:contract reads the framework’s optional_module and optional_attr as optional dependencies.

1.49

• feature:release refuses a revision id longer than 32 characters. See Migrations.
• feature:contract makes a link under has_endpoint an optional dependency. See Optional dependencies.
• The neutral app finds its platform by what each piece does. See The platform.
• feature:translate works on any working copy. See feature:translate.
• The CLI writes from its own templates, never a checkout in the workspace. See The CLI.

1.48

• F-CSP-UNAPPROVED gives one line per directive to approve. See Phase 7. Frontend.
• Every build lints a feature’s globals against the page it declared. See Globals of the page.
• Vendored wheels are fetched and checked. See Vendored wheels.
• F-CDN is an error for a feature with frontend/.
• The shell bundles the singleton it provides. See A feature with frontend/.

1.47

• product:validate checks the features’ bundles in a seventh phase. See Phase 7. Frontend.
• docker/frontend.lock.json records every bundle the image installs. See docker/frontend.lock.json.
• product:frontend:audit audits the bundles and writes their SBOM. See product:frontend:audit.
• splent.licenseTexts gives a package its licence file. See Licences and audit.

1.46

• A feature’s own JavaScript dependencies in frontend/, built in the SPLENT toolchain image. See A feature with frontend/.
• feature:compile, feature:npm and feature:frontend:init. See feature:compile, feature:npm and feature:frontend:init.
• The release builds and gates the bundle, its licences and its audit. See Licences and audit.

1.45

• spl:publish with a product selected. See spl:publish.
• The deploy artifacts follow the pins. See After a pin changes.
• product:validate --model and --pyproject check candidates. See A candidate pyproject or model.
• product:derive --dev --skip-validate. See Deriving past a failed pre-flight.
• Nothing of root’s in the working copies. See Startup scripts.

1.44

• SPLENT_APP=<product> splent <command> for another product. See Another product for one command.

1.43

• A feature’s tag carries its frontend bundle. See feature:release.
• The CI test job fetches the line’s model. See Continuous delivery.

1.42

• A product’s own commands, splent product:<name>. See product:commands.
• [tool.splent.test] env for a product’s own tests. See product:test.

1.41

• product:params. See product:params.
• SPLENT_MIGRATE_ON_START and db:status --check. See Startup script integration.

1.40

• Parameter nodes in the feature model. See Letting a value select features.

1.39

• product:validate checks parameters in a sixth phase. See Phase 6.
• A breaking schema change needs a major version. See Parameters.

1.38

• A feature’s tests run in a neutral app when the product does not declare it. See The neutral app.

1.37

• product:test runs the product’s own tests.
• check:vendor finds Keenthemes code. See check:vendor.
• The start migrates once, under a database lock. See db:upgrade.
• clear:uploads empties the protected uploads. See clear:uploads.