Changelog.

Every version of the free plugin, newest first. Versions before 1.0 are development versions, published so you can see how Snipfire got here.

0.15.0 Latest

New: the snippet library. 70 ready-made, tested snippets in 10 packs, including a Greek e-shop pack. Install from Snipfire > Snippet library, the classic screen, wp snipfire library or the REST API. Updates keep the settings you changed.
New: WordPress abilities to list and install library snippets.

Renamed to Snipfire. The shortcode is [snipfire], the WP-CLI command wp snipfire, the REST API snipfire/v1, and snippets are stored in wp-content/snipfire/.

New HTML locations: before or after paragraph N, before or after the excerpt, and in post lists before or after post N or between posts (block and classic themes).
Header & Footer screen: three boxes for code in the head, after <body> and in the footer, each a snippet with history and conditions.
Files: ads.txt, app-ads.txt, llms.txt and /.well-known/security.txt served by WordPress, and extra robots.txt lines. WP-CLI: wp snipfire files.
Shortcode finder: see where snippet shortcodes are used, spot ones that print nothing, and rewrite other plugins' shortcodes to Snipfire's. WP-CLI: wp snipfire shortcodes.
See who else has a snippet open, and get asked before a save overwrites someone else's newer version.
WordPress abilities (WordPress 6.9+) for AI assistants and the MCP adapter: list, read, check, save and switch snippets. Off for outside tools until you switch them on in Tools.
SNIPFIRE_DISABLE_PHP in wp-config.php turns off PHP snippets for everyone; DISALLOW_UNFILTERED_HTML makes Snipfire view-only.
Import from Post Snippets and Woody Code Snippets. WPCode's paragraph, excerpt and post-list locations now come across exactly.
WP-CLI: wp snipfire list takes --folder, --hook and --fields; create and update take --position.

Every snippet has a permanent ID that travels with it in exports, so the same snippet is recognised on other sites (used by Snipfire Pro's Git sync).
WP-CLI: wp snipfire create and update take --folder, --description and --tags.
Copies are named "Copy of …" in your language.

Snipfire is now the free core; SCSS/LESS, cookie consent, testing mode, the hook finder, team access, the activity log and the visitor, language and WooCommerce cart conditions move to the Snipfire Pro add-on.
The editor runs on WordPress's own React, so it loads faster.
Snippet settings that need Pro are kept, and fail safely without it: a snippet waiting for cookie consent doesn't run, one in testing mode runs for nobody, and SCSS keeps its last compiled CSS.
The history keeps the last 10 versions of each snippet.

Translation ready: every screen, message and label can be translated, and Greek is included.
Each person sees Snipfire in their own profile language.
The editor toolbar wraps instead of overflowing when labels are longer.

Team access: give each WordPress role no access, view only, CSS/JS/HTML without PHP, or full access. Administrators always have full access.
Activity log: see who created, edited, switched on or off, deleted or restored each snippet, which snippets were switched off after an error, and who changed settings. Filter it by snippet, person or kind of change.
WP-CLI: wp snipfire access, wp snipfire log.

Visual hook finder: click "Hooks" in the admin bar on any page to see every WordPress, WooCommerce, plugin and theme hook labelled right where it fires.
Click a hook to see what it passes, what's already attached at which priority, and which snippets run there, then add HTML or PHP on it in one click.
The side panel also lists hooks in the page head, actions that run before the page (init, template_redirect…) and the filters used on the page.

Cookie consent: JS and HTML snippets can wait until the visitor accepts cookies (statistics, marketing, preferences or functional). They run the moment the visitor accepts, without a reload, and it works with page caches.
Works with Complianz, CookieYes, Cookiebot, Borlabs Cookie, the WP Consent API and Google Consent Mode v2 (Real Cookie Banner and most other consent tools).
New "Cookie consent given" condition for PHP snippets.
Tools > Cookie consent shows the consent tool Snipfire found and what happens without one. WP-CLI: wp snipfire consent, --consent on create/update.

WooCommerce conditions: cart subtotal, items in cart, cart contains product or category, customer has bought a product, customer's paid orders (first-time buyers), and the order-received (thank you) page.
Visitor conditions: referrer, country (from Cloudflare and other CDN/host headers, or WooCommerce geolocation) and language (WPML, Polylang or the site language).
The rule picker is grouped (Visitor, Page, WooCommerce, Date & time, Site) and each new rule explains what it checks.
WPCode referrer rules are now imported.

History: every change to a snippet keeps the previous version. Compare any version side by side with what's in the editor, load it into the editor, or restore it in one click (the version it replaces is kept too).
Testing mode: set a snippet to "Only testers" and it runs only for admins and people you send the preview link to. Visitors don't see it until you click Go live.
Admin bar item listing the snippets in testing; preview visitors see a small badge with an exit link. Preview pages are never cached.
WP-CLI: wp snipfire revisions, wp snipfire restore, wp snipfire preview, and --mode=test on create/update.

SCSS and LESS: CSS snippets can be written in SCSS or LESS and are compiled when you save. Errors show on the right line, live while you type.
Partials: pull other SCSS/LESS snippets in by name (@use 'variables';, @import 'mixins';). Changing a partial recompiles every snippet that uses it.
@use 'sass:math', sass:map, sass:color and the other built-in modules work, as do @use ... with (...) and @forward.
A typo in a live SCSS/LESS stylesheet doesn't take your styles off the site: the last version that compiled stays live until it's fixed.
WPCode SCSS snippets are imported as SCSS source instead of compiled CSS.

Import from WPCode (including its global header/footer boxes), Code Snippets, FluentSnippets, Header Footer Code Manager, Simple Custom CSS and JS, the Customizer's Additional CSS, and WPCodeBox (beta). Locations, priorities, tags and conditions are carried over; anything that can't be matched exactly is flagged for review.
One-click switch over: snippets are switched off in the other plugin and on in Snipfire, and the site is test-loaded. The other plugin's shortcodes keep working.
WP-CLI: wp snipfire import-from <plugin> [--dry-run] [--switch].

New editor app: Monaco (VS Code) editor with WordPress, WooCommerce and PHP autocomplete, hover docs, parameter hints, hook callbacks, Emmet, Prettier formatting and live error checking.
Folders, search, filters, drag and drop, bulk actions, duplicate, export from the editor.
Fix: fatal errors before any output now switch the snippet off too.

First development version: core engine, basic admin screens, REST API and WP-CLI.

Snipfire Pro follows the same version numbers, and its changes are listed under the version they shipped with. What's next

Importing changes nothing until you switch over, and your old shortcodes keep working.