Changelog

Every release of Sabline, newest first, one page for each major version. The text is CHANGELOG.md's.

This project was called Velaris until 8.6.0; every entry below 8.6 uses the name it had at the time, which is what the record is for. docs/renamed.md says what moved where.

8.x: 8.6 to 8.5 #

• 8.6 - The name
• 8.5 - Taste

8.x: 8.4 to 8.3.1 #

• 8.4 - The kernel holds the line
• 8.3.1 - The documentation, as a site

8.x: 8.3 to 8.2.1 #

• 8.3 - What a run can show
• 8.2.1 - Two things that should have been red

8.x: 8.2 to 8.0 #

• 8.2 - Held to it
• 8.1.1 - The proof cache can no longer lie
• 8.1 - Receipts, and what a policy can ask
• 8.0 - What the socket reaches, and other things the audit now says

7.x #

• 7.2 - Releases that tag themselves
• 7.1.2 - The proof cache could be lied to
• 7.1.1 - 7.1.0 did not import on Python 3.10 or 3.11
• 7.1 - What an upgrade gained
• 7.0 - A secret you cannot look at

6.x #

• 6.0 - Secrets that cannot be printed

5.x #

• 5.0.1 - check_library.py runs on Linux and macOS again
• 5.0 - The default is io, not everything

4.x: 4.4 to 4.2.1 #

• 4.4 - A platform that lets its customers write code it can audit
• 4.3.4 - The npm wrapper picks the right Python, and says when it cannot
• 4.3.3 - velaris mcp, so the npm package can start the server too
• 4.3.2 - The card's true size, and a registry manifest on the current schema
• 4.3.1 - A discount that cannot go negative, and a timeout that says it timed out
• 4.3 - Money, which is not a float
• 4.2.1 - The author name, capitalised correctly

4.x: 4.2 to 4.0 #

• 4.2 - A producer for the capability predicate
• 4.1 - Conformance you can run, provenance you can check
• 4.0.1 - The review read the old files from the wrong place
• 4.0 - The operator sets the limits, and the capability surface cannot widen quietly

3.x #

• 3.4 - The doors are locked, and the findings go where findings go
• 3.3 - The capability check now means what the spec says
• 3.2 - The capability format, published as a spec
• 3.1.1 - A pool test that passed for the wrong reason
• 3.1 - A pool that keeps its budget, memory caps on Windows, and a lockfile
• 3.0 - Budgets that name paths, hosts, counts, and secrets

2.x: 2.63.1 to 2.40.1 #

• 2.63.1 - The memory cap claim, narrowed to where it holds
• 2.63 - What a security reviewer looks for
• 2.62 - Loops that provably end, and a corpus built to fool it
• 2.61 - A table anyone can rerun
• 2.60 - The ffi cliff becomes a permission
• 2.59 - Time and memory limits, prompted by a review bot
• 2.58 - Ready to submit to the frameworks
• 2.57 - --strict, from a question on r/Compilers
• 2.56 - Seamless means tested, not claimed
• 2.55 - Four more doors
• 2.54 - A door for languages that are not Python
• 2.53.1 - The library suite knows what needs the prover
• 2.53 - Setting it up should not be a chore
• 2.52 - Velaris from inside other programs
• 2.51 - Smaller per-call costs, and an honest note about the ceiling
• 2.50 - Function values carry their surroundings
• 2.49 - The card's gaps were hiding three real bugs
• 2.48 - Speed, without touching a single guarantee
• 2.47 - The periphery round
• 2.46 - Contents, not just lengths
• 2.45 - The road from 84
• 2.44 - Everything the adversarial report found
• 2.43 - The prover crosses the loop boundary
• 2.42 - Findings from a model that installed it and tried to break it
• 2.41.2 - A loop no longer hides a divide by zero
• 2.41.1 - The card worked, and the first program it produced found a bug
• 2.41 - Written by a model, audited by you, run in a box
• 2.40.1 - Leading with the sandbox

2.x: 2.40 to 2.0 #

• 2.40 - Running a program you have not read
• 2.39.1 - The refusal harness knows what needs the prover
• 2.39 - The editor asks for what the compiler already knew
• 2.38 - Testing the places languages break
• 2.37 - A stress test written in Velaris
• 2.36.4 - The Action has its own name
• 2.36.3 - A picture of the point
• 2.36.2 - Somewhere to start
• 2.36.1 - Two-part tags publish the extension again
• 2.36 - A tool worth running, and errors that read like a language
• 2.35 - Dates as values, HTTP with headers, and a way in for others
• 2.34 - Unattended work, and building for machines you do not have
• 2.33 - A number a team can watch, and an image to run it in
• 2.32 - The editor knows what is proven, and CI is one line
• 2.31 - A standard library that reaches outside
• 2.30 - The language reference, and a position on concurrency
• 2.29 - Remembered proofs
• 2.28 - velaris build: hand someone your program
• 2.27 - Handles: real libraries, not just functions
• 2.26 - JSON, and calling Python with real data
• 2.25 - Reaching the outside world, visibly
• 2.24.1 - The extension follows the language's version
• 2.24 - Lists of text, and split
• 2.23 - Libraries you can actually share
• 2.22.1 - First extension publish
• 2.22 - The editor extension, ready to publish
• 2.21 - Watching a program run, and case-changing proofs
• 2.20 - Whole numbers have a size, and outgrowing it is an error
• 2.19 - pip install velaris-lang
• 2.18.2 - Minimal-mode expectations for the newest proofs
• 2.18.1 - Releases stay green
• 2.18 - Records holding lists, and publishing
• 2.17 - for loops, tests in Velaris, and text containment proofs
• 2.16 - Catching the next one, a third app, and a current tutorial
• 2.15.1 - Native text building, made portable
• 2.15 - Native text building (the arena)
• 2.14 - Native text reads, and proven functions run fast
• 2.13 - Native lists
• 2.12 - Lists of lists, proven
• 2.11 - Invariant inference (the boring ones, for free)
• 2.10 - Contracts on function values
• 2.9 - Map proofs
• 2.8 - A second real app, and Text ordering
• 2.7 - Reading a codebase
• 2.6 - Division proofs, and seeing what your code promises
• 2.6 - Division proofs
• 2.5.1 - One problem, one message
• 2.5 - Namespaced imports
• 2.4 - The everyday things
• 2.3 - Public launch polish
• 2.2 - Out-of-the-box readiness
• 2.1 - Documentation site
• 2.0 - The builtins keep the language's promise (BREAKING)

1.x #

• 1.20 - sort_by + ledger reports
• 1.19 - Standard library sprint
• 1.18 - Float proofs (real IEEE-754)
• 1.17 - Failure-aware proofs
• 1.16 - Quantified list proofs
• 1.15 - Native Float and Bool
• 1.14 - Record proofs
• 1.13 - The first real app
• 1.12 - Continuous integration
• 1.11 - Language server
• 1.10 - Formatter
• 1.9 - REPL
• 1.8 - Real installation
• 1.7 - Generics + first stdlib
• 1.6 - First-class functions
• 1.5 - Unignorable failure
• 1.4 - Maps
• 1.3 - Float
• 1.2 - Browser playground
• 1.1 - Escapes + editor
• 1.0 - Testers' release

0.x #

• 0.x - The climb