Reference

Changelog

Each release of the LexLint plugin bundle since 1.40.0, newest first. Update the plugin in your client to get the newest. In Claude Code that is claude plugin update lexlint@lexlint, then restart your session.

1.48.1

2026-10-04

• The command in the procedure that prints the run after run_lint could not be pasted into a shell: a single apostrophe in its text ended the quoted program early, and the shell stopped with a syntax error. It now runs as written, and prints the same words as before. Nothing you declare or call changes.

1.48.0

2026-10-03

• A run that does not say whether a public body runs or buys the software now says so itself. Each jurisdiction where a law binding only public bodies matched carries one info line counting them, and set_profile asks the question in its next step when the answer was not sent. The same law no longer appears at two severities in two sessions without a reason given.
• A strategy, a charter or a regulator's guidance that matched your declaration is no longer reported as a duty. These records bind nobody on their own, so one info line per jurisdiction names them as context instead.
• generates_content now means output that reaches the app's users or the public. A tool whose AI output only its own team reads does not declare it.
• run_lint takes brief: true, for a client with no LexLint procedure that shows findings to a person. Each finding comes back as one line: its summary and first duty clipped to 160 characters, with the citation, link, when the law binds and whose duty it is. On a customer's 61-finding run that is about 3,700 words where the full run is about 25,000. The plugin never sends it: the procedure needs the full findings to write lexlint.yml.
• Every run_lint result carries replay, a short reference to quote when you tell us about a run. It names the bundle, the law library build, the moment the run was judged and a digest of the declaration, so we can rebuild exactly that run. Nothing about the run is stored to make this work; the feedback step now puts it in the summary for you.

1.47.0

2026-10-03

• When a court has blocked a law, struck it or part of it down, or upheld it after a block, the finding now says which ruling did it. A new field, court_action, carries each ruling's name, its court, the day it was decided, what it did, the parts of the law it reached when it reached only some, where it stands now (an appeal filed, affirmed, reversed) and its case page on LexLint, plus a flag when a suit against the law is pending. It is absent when no court has acted, which is most laws.
• The run printed after run_lint adds a line under any law a court acted on, for example "blocked 2025-08-29 by Kohls v. Bonta (United States District Court for the Eastern District of California)", and "under challenge in court" when a suit is pending. The brief for counsel names the ruling the same way, linked to its page.
• lexlint.yml keeps court_action on each finding, and the bundle's schema declares it. Nothing you declare or call changes.

1.46.2

2026-10-01

• LexLint's body of law is now called the law library wherever you and your agent read it: the tool and schema descriptions, the text the server returns, the written procedure, the plugin's commands and README. It used to be called the corpus. Only the word changes. No key, field name, value or step is different, and corpus_built_at keeps its name, so a client that reads it is not affected. The run block the procedure prints labels its third line law library, where it read corpus.

1.46.1

2026-09-30

• The bundle's descriptions now name content-moderation law among the topics the lint reads: the liability of a service for what its users post, notice-and-takedown, and moderation transparency. A profile that declares operates_social_platform meets it. Nothing you declare or call changes.

1.46.0

2026-09-30

• A run now opens in the shape https://lexlint.io and https://developer.lexlint.io show a run in, printed straight after run_lint and before anything is merged: what was declared, where the app operates, by flag and name, and the date of the corpus; then a block for the lead finding in each declared place and for every finding for counsel, each with its place, the law, when it binds, the duty in full, the date it was read against its source and the address of its law page; then a count of what the block shows and of the rest.

1.45.1

2026-09-29

• The bundle now carries this changelog, CHANGELOG.md, with one entry per release, newest first. Read it in the bundle or at https://developer.lexlint.io/changelog on the developer site.
• The procedure's pointer to LexLint's law pages, which had been a bare domain name, is now the full address https://lexlint.io/law

1.45.0

2026-09-29

• A profile can now declare a public-sector role, profile.public_sector: body for software a public body runs, supplier for software sold to or run for public bodies, both, or none. set_profile, run_lint and upload_lint_run all accept it.
• With the role declared, each requirement is routed by who owes it. Every instrument finding carries owed. A duty that binds you stays in the finding's requires. A duty that binds only bodies you are not is reported as information, with its lines kept in requires_elsewhere.
• A duty that your public-sector customer owes and meets through your software arrives as its own customer_duty finding, placed right after the instrument finding it was split from.
• A caller that does not declare a role gets exactly the output it got before.

1.44.0

2026-09-29

• A state or other sub-national place now reads with its country code first, as "US-California", where it used to read "California (US)". The code, a hyphen and the name take about as much room as a flag emoji and its space, so a Place column lines up in both command-line clients. No field is added or renamed.
• The procedure's flag rule and its examples use the new form, and the plugin schema's description names both.

1.43.1

2026-09-29

• The copyright line in the bundle's LICENSE file now names the holder as UnGovr, with no company-type suffix. No tool, schema or procedure behaviour changes.

1.43.0

2026-09-28

• Every run_lint finding and every set_profile coverage row for a country, the European Union or the United Nations now also carries jurisdiction_flag, the flag emoji for that place. A state or a city carries none and never borrows its country's. The field is declared in the plugin's schema, and a merged manifest keeps it.
• The procedure prints the flag, then a space, before the place name in every table and list, and the keyless first-run preview table prints it too.

1.42.0

2026-09-26

• Every run_lint instrument finding, and every instrument get_law returns, now carries in_force, which says when the law binds. It is declared in the plugin's schema, a merged manifest keeps it, and lifecycle stays for existing clients.
• The procedure prints each finding's in-force words, in_force.words, wherever it says when a law binds.

1.41.1

2026-09-26

• The aggregation topic is labelled "Reuse law", not "News aggregation law".

1.41.0

2026-09-24

• The procedure names the communications topic and the three facts it adds.
• The automated_outreach activity no longer borrows deploys_chatbot's categories. It now reaches the communications topic's rows, so a profile that declares it gets those rows in place of chatbot-disclosure rows, and its findings change.

1.40.3

2026-09-23

• /lexlint-key checks a key with check_access.
• LexLint no longer says your key is forwarded to a separate data service. The LexLint server checks it itself. Where get_law holds no data for a jurisdiction, its note now points at https://lexlint.io/law for coverage.

1.40.2

2026-09-21

• Step 1 no longer leaves a row marked ask when the evidence in hand settles it, and it asks an open ask row again before it sets the profile, so a one-word yes can no longer silently drop that row.
• Step 1 resolves the app's domains before it shows the declaration table.

1.40.1

2026-09-21

• Step 1 proposes the declaration from the code, and you confirm it, on every client.

1.40.0

2026-09-21

• A compact upload's app_scope reaches the portal as the scope object its schema requires.