Skip to content

Releases

Release notes for tagged versions of Artist Alley, newest first. Each section summarises what that release shipped; the complete record of every change is the upstream CHANGELOG.md. See Installing for how to run each release. Where a section has been corrected since it was first published, a dated note says what changed.

Versioning follows the milestone model: v0.1.0 is the first tagged release, v1.0.0 marks out-of-beta. See ADR 0057 for the v0.1 baseline.

VersionReleasedTag
v0.11.1 GitHub
v0.11.0 GitHub
v0.10.2 GitHub
v0.10.1 GitHub
v0.10.0 GitHub
v0.9.1 GitHub
v0.9.0 GitHub
v0.8.0 GitHub
v0.7.0 GitHub
v0.6.0 GitHub
v0.5.2 GitHub
v0.5.1 GitHub
v0.5.0 GitHub
v0.4.0 GitHub
v0.3.1 GitHub
v0.3.0 GitHub
v0.2.0 GitHub
v0.1.2 GitHub
v0.1.1 GitHub
v0.1.0 GitHub

Generated from the GitHub releases API, refreshed every six hours. Notes for each version follow below.

Reproducible test runs: the project’s automated checks now run on GitHub-hosted machines against public, pinned sample datasets, and open security advisories in web dependencies are resolved.

The same sample data on every run. The dataset-based checks now use fixed editions of the site_a and site_b sample libraries. Each run pins the edition and verifies its files before seeding, so a failing test can be repeated against exactly the same data, and contributors can run the same checks from public data without the project’s private archive. A daily full-corpus check also pages through every post and asset to catch paging mistakes that a smaller library could miss.

Checks run on GitHub-hosted machines. Browser tests, integration checks, image builds and the release workflow moved from self-hosted machines to GitHub-hosted runners.

The dataset editions were published as provisional prereleases, accepted by the project owner; publishing them is not a per-file rights clearance. The demo seed and its Kaggle dataset have not changed in this release.

  • Web dependencies resolved past fourteen advisories. dompurify 3.4.18 (including one critical advisory), zod 4.6.7, vue 3.5.45, undici 7.30.1 and @ai-sdk/provider-utils 4.0.33 (#1556).
  • The License page describes community mode as it is. It no longer says community mode is capped at 15 seats and 20,000 assets: community mode applies no seat or asset cap. LDAP and SAML sign-in and multi-tenant deployments stay unavailable without a license that includes them, and no such license is offered today (#1502).
  • Release images carry accurate metadata and tags. The image description no longer advertises a commercial license, a release started by hand from main now publishes the same version tags as a tag push, and the release announcement names a tag that was actually published (#1503).

Making and describing work: helping artists create, describe, organize, find and manage their work without turning the archive into paperwork.

Better post creation and publishing. Posts now have real drafts, a full post editor, scheduled publishing and per-post comment controls, with a full-page creation flow alongside the quick upload dialog.

Metadata that works like a studio system. Custom fields can be required, read-only, conditionally shown, grouped into tabs, validated and edited after upload. Metadata can be updated across many files at once, with a preview of exactly what will change and safeguards against stale edits and permission mistakes.

Stronger search. Search understands file kinds such as video, 3d, audio and pdf and supports richer advanced-field queries. Advanced search and saved searches also accept new commands such as !lastN, !list and !nopreviews; the main search bar is unchanged.

Better upload and asset workflows. A 3D model uploaded with its referenced textures keeps those files together automatically, pages refresh correctly after quick uploads, and asset owners can see where their files are used.

Clearer AI provenance. Artists can declare whether work is AI-generated, AI-assisted or made without AI. The declaration is visible in the interface, and browsing can hide purely AI-generated work without hiding mixed or undeclared work.

A more dependable demo dataset and test pipeline. The seed dataset, its archive publishing, regression coverage and CI integrity were all strengthened, so the demo library and automated tests better reflect what the application promises.

  • A field value you may not read is no longer sent to the browser. Forms that decide whether to show a control now ask the server what you may read on that record, and the protected value itself stays on the server (#1173).
  • Marking an upload as mature is no longer silently dropped. The setting could be lost when the box was ticked after a file had been added, or when the create response came back without it (#1239).
  • A wrong API address now answers 404. Released builds answered a mistyped, removed or not-yet-shipped API address with “200 OK” and the site’s web page, so a program could not tell a missing endpoint from a working one (#1161).
  • The first-boot message no longer announces a password it did not set. When the server repaired an existing administrator’s missing role, it reported a freshly generated password it had not applied and, where the generated password is kept in a file, overwrote the real one there. It now says the password is unchanged (#1274).

Seed coverage for mature content, and a cover editor that uses its room.

The sample library can finally show the mature-content controls working. Those controls shipped in v0.10.0: an artist marks a work, each account opts in or out, the instance has a master switch, and work you have not opted into is simply absent rather than blurred-and-teasing. But nothing in the sample library was ever marked, so on a fresh install the whole system was invisible. Twelve public-domain classical works are now labelled (the kind of fine art a museum genuinely flags), and the labelling is a required part of the test fixtures, so it cannot quietly disappear again.

The collection cover editor spends the space it was given. Choosing a cover used to mean peering at one clipped row of pictures inside a dialog that left half its height empty; now the picker fills the room, and the crop area grows once a picture is chosen.

The listening release: two days of real use, and everything it turned up.

Nothing in this release came from a plan. It came from working in the app and writing down what got in the way: 28 fixes and refinements across search, browsing, collections and accessibility.

Search stops guessing at what you meant. Typing no longer re-runs the search under you: suggestions appear as you type, results change when you press Enter. A suggestion never offers a word that finds nothing, because suggestions are now drawn from the same rule the search itself runs. Advanced search dropped its developer vocabulary and copes with real catalogues: a field with thousands of values becomes a type-to-filter box rather than an endless wall of chips. The search button now opens Advanced search, a dedicated page that combines the typed query builder with per-field metadata filters.

Browsing keeps up. Endless scrolling now loads far enough ahead that fast scrolling never lands on blank space; the trigger had been watching the wrong thing entirely, so its head start never applied. Grid tiles ask for a picture sized to the tile instead of stretching the smallest one. The sort control gained a type filter that looks inside posts, so a post carrying an ebook answers the ebook filter even when its cover is a painting; a pack whose contents are all one kind wears that kind’s icon.

Visitors can browse public work. Marking a post public had never actually worked: the option was there, the server refused it. Now it works, instances that allow anonymous browsing serve public work to visitors with every privacy rule verified on that path, and signed-in members see public work in their own feed instead of only their organisation’s.

Collections hold posts. Loose files stay in your own space until you make them into a post. Collection covers grew up: one cover for the collection card, a different one for the featured strip, each positioned by dragging a crop box with zoom so an off-centre subject can be framed, and the picture can come from the collection, from your files, or from an upload you do right there. Editing it all happens in one dialog with pages, not a window on top of a window.

Every menu works from the keyboard. Several menus, including sign-out, could not be reached by keyboard at all. They can now, and a test walks the page to keep it that way. Spatial tools that genuinely need room say so on small screens instead of cramming.

  • A dependency guard was re-armed. The version pin that protects a YAML library from known advisories had fallen behind two newer ones; it now requires the patched version (#1005).

The browse experience release: search sealed, the wall rebuilt, every view given its own feel.

The browse wall no longer improvises. The masonry view computes every tile’s placement deliberately: no more growing gaps, no losing your place when more work loads in, no reshuffling under your cursor. Featured collections ride a wide slider at the top at a fixed, designed size, and operators can place a full-width promo band in the feed for signed-in readers or for everyone. A promo band meant for everyone reached signed-out visitors only from v0.10.1, the first release in which they could load the feed.

Every view mode has its own identity now. Grid is a visual wall that shows details when you hover: the artist, the work’s title, what kind of asset it is. Thumbnails are a working surface with visible controls. List is for metadata, with resizable columns. The feed is for reading. Each is tuned as its own thing rather than one layout stretched four ways.

Mature content is a choice at every level. Artists mark a work with one checkbox at upload. Every account chooses whether to see marked work; the operator chooses whether the instance allows it at all. The rule follows the work everywhere it echoes: previews, collection covers, counts and featuring. Administrators are exempt so that they can moderate: an administrator sees mature work without opting in.

Teams and tags became ways to read the feed. A rail above browsing filters the feed in place by team, tag follows work the same way, and the rail is yours to curate.

Selection works like a desktop on the browse feed. On the browse feed, drag a box around tiles or shift-click a range, and act on all of it. Inside a collection, list view supports a shift-click range, but there is no drag box.

Search stopped leaking what it hides. A work you are not cleared to see no longer shows up in text search through its withheld title, in tag suggestions, or in counts. The individual fixes are listed under Security.

  • Comment threads respect post visibility. The comments on a post, and five related endpoints including two write paths, no longer answer callers who cannot see the post itself (#1132).
  • Annotations respect asset visibility. Reading or writing text annotations now requires being able to see the asset’s content (#1135).
  • Mature works stay hidden in every picture. Collection cover mosaics, chosen covers, team pictures, saved searches and document search now apply the same mature-content rules as every list (#1147).
  • A restricted file’s title can no longer be pieced together through search. Files you are not cleared to open are still listed, but their withheld titles no longer answer text searches (#902).
  • Tag suggestions no longer come from posts you cannot see. The search box’s tag completions were drawn from every post on the instance, including ones the caller was not allowed to see (#1075).
  • Embedding queries no longer rank files you are not allowed to open. The backend query that compares files by their AI embeddings, which runs only when an operator has connected an AI model server, considered every file on the instance, including files whose picture the caller is refused, so a file’s rank could hint at what a locked file looks like. It now leaves those files out (#1066). This was a permission fix in backend code; image similarity search is not available yet as a feature of the app.
  • An opted-out name stays hidden. Someone who opts out of appearing to logged-out visitors is no longer named as the owner of files inside a public collection or post (#1023).
  • A vulnerable package is out of the published image. The 3D preview renderer’s browser driver pulled in an archive-unpacking library with a known advisory; it no longer ships (#1070).
  • The admin area turns away people who don’t administer anything. It used to let every signed-in account in to a page of two tiles; an ordinary account now gets a plain “you don’t have permission” page (#962).
  • Every build path now states the right licence. Tagged release builds already reported AGPL-3.0 correctly, but the image licence label said BSD-3-Clause on the rolling edge image and on images built from a copy of the source, which covers most self-hosted installs. Both build paths now report AGPL-3.0-only and also agree on the project’s description (#1091).

A security patch, and nothing else.

A YAML parser bundled deep inside the 3D preview tooling had a flaw that let a malformed document burn CPU. Nothing in the product fed it untrusted input, so there was no way to reach it, but the vulnerable copy was inside the published image, and anyone scanning that image would see it. It is now the fixed version (#1038).

No functional changes.

Permissions became one rule, deleting became reversible, and the surfaces that were only half there got finished.

Being allowed to change something no longer implies being allowed to see it. A team lead can correct a title without being cleared for the artwork behind it. Editing and deleting a file also gained the ownership check they had been missing, listed under Security below. The same check lets a team-scoped grant manage that team’s files through the API; the web app only offers those controls to a file’s owner and to accounts that hold the permission across the whole instance.

Deleting is reversible, and visible. Every account has a trash page listing what it deleted and how long is left to recover it. Deleting anything offers Undo. If someone else removed your work, you can ask for it back, and only the person who deleted it, or an administrator, can decide.

The feed is a real feed. Feed view now shows who made each post, the image at its own shape rather than cropped square, and like, comment and share where you would expect them. Reacting works from the feed, and the count moves when you press it.

Operators choose which browse layouts their install offers. Grid, masonry, thumbnail, list and feed were shown to everyone, always. An operator can now pick, and anyone already using a layout that gets turned off is moved to one that works, keeping their old choice in case it comes back.

The control bar comes back when you reach for it. The layout and sort controls slide away as you scroll and used to return only when you scrolled back up. Moving the pointer toward them brings them back.

You can save someone else’s post to your own collection. Collections could already hold other people’s files; posts were the missing half. What lands in your collection is a reference to their post, not a copy, and it changes nothing about who can see it.

Studios have a home page, and you can follow them. Plus a page per metadata field for operators, an edit page for files, the interface language applying the moment you sign in, and one keystroke meaning one action across the viewer.

Underneath, the image pipeline stopped running out of memory: measured rather than guessed at, with the identical workload going from being killed at its ceiling to finishing with room to spare at no cost in speed.

  • Anyone signed in could edit or delete anyone’s assets. Editing and deleting a file now checks that you own it or hold the permission to manage it (#930).
  • Putting someone’s work in a post or collection no longer makes it more visible. A restricted member of a public post or collection no longer exposes its title, description, location metadata or blurred preview (#883).
  • A restricted asset no longer hands out its metadata. A restricted asset you cannot open no longer returns its full metadata through the asset API, browse or search (#899).
  • A public collection no longer hands out its guest list to anyone signed in (#933).
  • Sharing a post no longer shows the recipient the rest of the guest list (#876).
  • You can no longer put someone else’s restricted work in your own post (#922).
  • A post’s cover picture now gets the same check as its other pictures (#941).
  • A post can no longer be labelled with a studio you have no tie to (#954).
  • Three known CVEs no longer ship in the published image. A library inside the 3D preview renderer carried them; it is updated, and the gap in image scanning that let them sit there is closed (#905).
  • A vulnerable copy of nanoid no longer ships in the site’s bundled packages (#1001).

Operator configuration, the admin config spine: an operator can now shape metadata, wording, and email without forking or restarting.

  • Controlled vocabularies are editable, and Keywords can grow. The options behind a select or hierarchical field are editable in place, and Keywords is now an open vocabulary: a term that does not exist yet is minted the moment you type it, and keywords are also learned from the IPTC metadata embedded in uploaded files. New terms reconcile behind the scenes rather than adding an upload-time decision.

  • Hierarchical fields got a tree editor. country ships as a closed tree of 24 countries grouped under 5 continents, and the nested terms of any hierarchical field are now editable through a dedicated tree editor rather than a flat list.

  • Rich-text fields render as formatted text. rich_text is a first-class field type, sanitised on the way in and on the way out, so a formatted description survives a round trip without becoming an attack surface.

  • Any wording the interface ships with can now be changed without forking. Admin → Content → Site text lets an operator override the copy the interface ships with; the override applies on this instance and any instance sharing the database, with no restart.

  • The emails this instance sends can be rewritten without forking. Admin → Content → Email templates lists every transactional email with its shipped subject and body, an editor, the exact fields each email exposes, a sandboxed live preview, and Revert.

  • Field administration is a grantable capability. fields.admin now exists as a real capability and is granted to the built-in Admin role, so an operator can delegate creating, editing, and deleting field definitions without handing over the whole install.

  • Operators can set their own instance logo, and profiling can be turned on when something needs investigating (AA_PPROF_ADDR).

  • Internal phase markers no longer show up in the interface. The muted markers that leaked internal release identifiers were removed in favour of plain language, though some “coming soon” labels still remain on features that have not shipped.

  • The browse feed’s “Team” and “Trending” buttons are gone, folded into the filter.

  • postcss moved past a path-traversal advisory. The web build’s copy of postcss auto-loaded source maps in a way that could be pointed at files outside the project; it is now on a patched version. Only the build was affected: nothing shipped to a browser, and no running instance was exposed (#848).

  • SSO provider credentials are no longer readable. The admin auth endpoint used to return each provider’s whole configuration, including the OAuth client secret, the LDAP bind password and the SAML private key, to any capability that could read system config. Those three are now write-only, and the configuration is one closed schema shared by every provider kind rather than a free-form map a future credential could hide in. The AI provider record was closed the same way (#718).

  • Re-seeding an instance no longer serves stale data until a restart. A seed run now broadcasts a cache flush every running instance honours, so a reseed is visible immediately.

  • Plus a long tail of correctness fixes: dates no longer land a day early, out-of-range field values are rejected instead of silently stored, an upload no longer reports success when the server refused its metadata, portrait photos and videos stop being laid out as landscape, hierarchical and yes/no fields work end to end, masonry respects each tile’s aspect ratio, nginx stops routing to a dead container after a recreate, and 3D models render with their textures (GLB, FBX, and the seed catalogue’s missing maps).

Browse correctness, visibility security, and a real seed catalogue.

Cards render correctly end to end. Tiles follow their image’s true proportions instead of being squared off; the masonry wall stops reshuffling tiles you are already looking at each time more results load; every asset type now fades up from a blur instead of flashing blank, including audio, 3D, video, fonts and ebooks, which previously had no placeholder at all; thin audio tiles keep their controls inside the tile, with the rest of the detail moved to a tooltip that follows the cursor; and cards stop downloading images larger than the space they are drawn in.

Assets with no preview picture (text files, documents, or a preview that simply failed) get a designed tile stating the file’s format and kind, rather than an anonymous “image missing” glyph.

Form controls meet the contrast floor. Form controls drew their border in the same colour as a divider rule, measuring well below the WCAG 2.2 contrast floor for a control boundary in both themes. They now clear it. Strengthening the resting border would have made the focus indicator invisible on 122 of those controls, so focus moved to a standard 2px ring.

The seed catalogue doubled. The bundled demo library grew from 971 assets at v0.6.0 to 1,947 at v0.7.0, and every studio in it now has real work to show: two had none at all, while one held nearly half of everything. Provenance is recorded per record so any item can be traced to its source and re-fetched.

Four separate leaks, found in one week, all the same underlying mistake: a read path that wrote out the “who may see this” rule itself instead of asking the one component that owns it. Each copy was correct when written; the shared rule moved and the copy didn’t. None was caught by a test. Two further fixes in this list concern who can see session IP addresses.

  • Private posts were readable by anyone signed in. Adding a visibility=private filter to the post list returned other people’s private posts (title and body) while opening the same post directly correctly refused. No special role was needed. The list and the single-post view now run the same rule, so they cannot disagree again, and a test enumerates the visibility tiers from the database itself so a tier added later is covered automatically (#660).
  • The IIIF manifest route had no permission check for signed-in callers, returning a collection’s name, description and full member list to any signed-in caller (#661).
  • A tag filter exposed unpublished work. On an install with public browsing enabled, adding a tag filter returned draft and archived assets that the unfiltered browse correctly hid (#657).
  • Related-asset and IIIF manifest routes leaked unpublished assets to anonymous visitors, and genuinely public collections returned “not found” to them; both now follow the shared rule (#661).
  • Session IP addresses became a separately granted permission, matching how the audit log already treated them (#573).
  • The account sessions page no longer shows client IP addresses. /account/sessions returned the IP address of every session on the account, which on a shared demo account showed each visitor the addresses of earlier visitors; session lists no longer include IP addresses (#567).
  • Search works again for signed-in users. Every authenticated query returned an internal error, because the search still asked for a column that had been removed (#650).
  • The server image is half the size: 3.64 GB → 1.82 GB. Blender is no longer packaged: it was roughly a third of the image, plus the ten X libraries it loaded at startup, and nothing in the product invoked it any more: every 3D format in the reference catalogue already rendered through the three.js worker. Formats with no three.js loader (.blend, .usd*, .abc, .x3d) get no generated thumbnail for now (the file still uploads, downloads and serves normally) and regain one when the Blender converter ships as an optional plugin. Nothing to do on upgrade; no configuration changed. arm64 deployments are unaffected: they never had Blender.

Public profiles, one viewing experience everywhere assets are shown, and a faster 3D preview pipeline.

  • Public profile pages. Every user now has a profile page (reachable by username or by a stable ref) showing their display name, avatar, and the assets, posts and collections a viewer is allowed to see. It reuses the same visibility rules as the rest of the site: anonymous visitors see only public work, and only when public mode is on. An owner can opt out of anonymous exposure only through the API; there is no setting for it in the app. This also cleared the last of the dead author and similar-asset links (#478).
  • Shared view controls everywhere. The browse view switcher (grid, masonry, thumbnail, list) and sort direction now appear on the profile and post-by-asset pages too, not just the main browse: one consistent control bar wherever assets are shown (#511).
  • Faster 3D previews, and multi-file models fixed. Open-format 3D previews (glTF/GLB, FBX, OBJ) now render through a headless three.js worker instead of Blender: much faster, and arm64 deployments get 3D previews for the first time (the Blender path was amd64-only). A multi-file glTF model (the model file plus its external data and textures) now renders correctly where it used to fail silently. Blender stays as an automatic fallback (#497, #498, #507, #508, #486).
  • IIIF tiles respect content permissions. A signed-in user who could see that a restricted, team-only or embargoed asset existed could still download its full-resolution IIIF image tiles; tiles now return 404 to anyone who may not read the asset’s content (#476).

Under the hood: a large CI-reliability and test-isolation hardening pass. Not user-facing, but it is why these shipped green.

Read-only viewers see the whole catalogue.

The public demo login used to hit blank “Preview unavailable” tiles on anything above the lowest tier; now it sees every tier of content.

  • A read-only content capability (#474). A new content.read.all grant lets a role read asset content at every sensitivity tier, and nothing else. It opens no admin surfaces and permits no writes, so the public demo viewer can browse the full catalogue without being an administrator. Granting it to a role is a deploy-side step (ADR 0060).

Promoted all of dev since v0.5.0: a patch version number, but a substantial release.

Two demo-surfaced fixes, a visibility-consolidation batch, and the accumulated foundation work.

  • Shareable, reloadable asset pages. Assets now have a real /assets/[id] page, so a link to an asset opens, reloads and shares correctly. Before this, clicking an asset inside a collection dead-ended on a “Not found” page; the tile linked to a route that never existed (#475). A build-time link-integrity check now guards against dead internal links (ADR 0068).
  • 3D previews on published builds, for the first time. Turntable thumbnails for 3D models (glTF / OBJ / FBX and more) had never generated on released images: the published image had shipped without the renderer, so every 3D asset showed no preview (#470). This release added it for amd64, with a build-and-render smoke so it can’t regress unnoticed.
  • Audit-log retention and export. The audit log gained a retention policy: retention periods are stored per event category, a category without its own period keeps a 7-year default, and a nightly pass purges expired events while skipping any event marked with a legal hold. This release added no API or admin screen to change a category’s retention or to set a legal hold. A function that anonymises a user across the log for a GDPR erasure request exists in the code, but nothing in the app calls it. The whole log can be exported as CSV or NDJSON over a date range, streamed so exports of millions of rows don’t exhaust memory; IP addresses are withheld from the export for callers who can’t see them in the live view.
  • The scheduled-actions engine. The engine that runs a stored action at a future time (changing an asset’s sensitivity, soft-deleting, changing state, or notifying) shipped with an admin API to list pending actions and cancel them, and each action runs atomically with its audit entry, so it either fully happens and is logged or fully does not. Operators could not create scheduled actions in this release: nothing in the API or the app created them. This is the generic engine (ADR 0020); the asset-gating features meant to use it, such as blur, reveal and a timed embargo lift, are still planned.
  • Content-visibility hardening. Soft-deleted collections no longer appear to signed-in non-owners, and the IIIF image path enforces the same visibility rule as the browse grid (#451, #460).
  • Two internal maintenance changes, with no change in behaviour. An unused audit query no longer selects the IP column (#458), and a new test covers the existing superadmin include_deleted gate at the handler level (#431).

Public mode: content is now reachable without an account, on an operator’s terms.

The visibility model gained a shared predicate, the routes that deliver an asset’s content started enforcing its sensitivity tier, and opening the surface surfaced and closed three pre-existing access holes in the foundation beneath it.

  • Public browsing is an operator choice, off by default. Anonymous access had no switch: any instance served its public content to the internet whether the operator wanted it or not. There is now a setting, enforced at the API rather than by hiding pages: turning it off means anonymous requests are refused, not merely unlinked. A fresh install starts private, and first-boot and password sign-in keep working with it off. Single sign-on was not available in this release and is not available yet; it is planned for v0.17.0.
  • A shared visibility predicate. Collections gained a public tier, and read paths gained a single visibility predicate to splice in instead of each writing out its own rule (ADR 0063). Posts gained the public tier in the database, but the post API refused to set it until v0.10.1. Some read paths did not use the predicate yet: the IIIF image path was brought under it in v0.5.1, IIIF tiles in v0.6.0, and the post list, the tag filter and the related-asset route in v0.7.0. Anonymous callers see published, public, ready content only. Browsing without an account now works: GET /assets, /assets/{id}, /collections, /collections/{id} and public image bytes all serve anonymous requests; every write path still requires authentication.
  • Sensitivity gates the asset content routes. The routes that deliver an asset’s content by asset ID (its original file, derived variants, HLS video segments and archive entries) previously checked only that a caller was signed in, so any authenticated account could download draft or restricted material through them. They now check the caller’s access, including the tier: team needs membership, and restricted and embargo are limited to the owner and administrators. A denied request gets a 404 rather than a 403, so the response cannot confirm that a hidden asset exists, and an error during the check also denies. Listing is deliberately unchanged: restricted assets stay visible as locked items rather than vanishing (ADR 0064, following ADR 0020).
  • A logged-out visitor has something to look at. Curated content can be featured for a public audience and the front page renders it. Featuring is now a placement, not a flag: the same collection can be featured publicly and internally at once, each with its own order, and an asset can be featured without wrapping it in a collection. It never widens access: a featured item renders only if the viewer could already see it.
  • Audit-log IP addresses are gated behind their own capability. Seeing what happened and seeing from where are now separate grants: system.audit.read returns the log without IPs, and a dedicated system.audit.pii.read is required to see them. The address is withheld at the API, not merely hidden in the UI.

Three pre-existing holes closed while opening the surface: the two asset and collection detail endpoints checked only that some caller was signed in, so any account could read another user’s private item by id; the collection list applied no visibility rule at all; and collection-contents enumeration was unchecked. All now run the same visibility decision.

Operator visibility: the async pipeline and the storage layer are now observable and manageable from the admin surface.

  • Jobs admin. The async job pipeline (derivatives and previews, plus AI embedding and transcription jobs when an AI provider is configured) previously could only be inspected with psql. New surfaces: queue (by status/type with age and priority), workers (lease state, stale-lease flag), live, failed (with last_error), kinds (per-type concurrency) and schedules, read-gated on system.jobs.read so a read-only operator can watch without holding system.admin. Requeue, cancel and concurrency edits require system.admin; a currently-running job is never touched by either.
  • Storage admin. Usage (deduplicated bytes on disk, originals vs derivatives, broken down by content type and backend) and variants (per-family inventory), read-gated on the new system.storage.read.
  • Storage integrity sweeps. orphan_scan reconciles the object store against the database in both directions; checksum_verify re-hashes stored bytes against the content-addressed key. Both run as batched, resumable job kinds and report into an admin surface. Findings are advisory; no destructive cleanup ships in this release.
  • About reports the real version, read from a new anonymous GET /build-info endpoint instead of a hard-coded placeholder; the displayed licence was corrected to AGPL-3.0-only.
  • Help is visible to read-only operators: documentation, shortcuts, about, release notes and support are explicit public admin tiles, identical on desktop and mobile (ADR 0061).

Infrastructure: storage backends gained an ordered, cursor-resumable List (ADR 0062); Dependabot grouped per ecosystem so routine bumps stay auto-mergeable; a pre-checkout stale-.git-lock sweep fixed intermittent self-hosted checkout failures.

Admin read-cap UI and foundation cleanup.

  • Admin UI for read-cap holders. The frontend half of v0.3.0’s read capabilities: the admin menu and route guard now gate each tile on a capability, so a read-only role (without system.admin) sees and can browse the sections its capabilities permit. The backend still enforces every write. One tile did not line up: the system log tile asked for system.config.read, while the log it opens reads the audit log, which requires system.audit.read.

Infrastructure: repo-wide gofmt normalisation behind a gofmt -l CI gate; a make release target codifying release prep (version bump, OpenAPI regen, drift check, promotion PR) without tagging; Dependabot github-actions group split; the steel secondary token wired into the Alert info tone.

Derivatives, read-only admin, responsive UI.

  • Media derivatives generated for seeded assets. aa seed now queues preview jobs for every seeded asset, as the upload path already had since v0.1.0, so a seeded instance gets col / hires / screen thumbnails plus sprites.jpg video hover-scrub sheets: the browse grid renders real thumbnails instead of 404ing, and videos get a slideshow preview.
  • Read-only admin access, on the server. A role can hold *.read admin capabilities, and six previously superuser-only surfaces (activities, featured, license, metadata-extraction, federation, requests) now answer read-only requests without the system.admin superuser cap. The admin menu still required system.admin until v0.3.1, so read-capability holders could browse those surfaces from the admin menu only from that release.
  • Responsive + accessible UI. Browse and navbar are fluid from a 390px phone to a 3840px / 32:9 ultrawide: an auto-fill grid where size is the lever and column count is the outcome (no breakpoint cliffs), an Instagram-style single-column feed view, hide-on-scroll chrome, and WCAG 2.2 AA target sizing on coarse pointers. Desktop layout unchanged.
  • Featured content curation is seeded, so the admin Featured rail and the public collections featured tab both show content on a fresh seed.
  • Operator-bug fixes. PATCH /admin/system/site now merges instead of blanking omitted fields (updating base_url used to wipe the site name); unroutable file extensions no longer mint guaranteed-terminal preview jobs.

Infrastructure: a CI/nightly stability arc (per-run compose isolation + resource caps, five stacked shared-daemon/host causes fixed) left the federation nightly green for the first time since 2026-06-21.

Admin surface unlock and public demo.

  • Admin tiles unlocked (Tier 1–2). The admin surface gained its first working tiles: an audit-log viewer (/admin/audit), per-user active sessions plus capability grants/revokes, resource requests, trash with soft-delete restore across assets/posts/collections, a system log view that reads the same audit log, and an API explorer served from the Go binary (/api/v1/openapi.json, replacing the external-spec fetch). Most of the menu was still to come: 37 tiles were live and 65 were still marked as future work.
  • AA_DEMO_MODE. Env-gated demo mode: a demo/demo credential hint and fill button on the sign-in screen, plus a read-only banner shown to every signed-in user while demo mode is on. Off by default; zero footprint on real installs.
  • Public read-only demo at demo.artist-alley.org: runs the release image behind a write-blocking nginx edge, seeded from the Layer-A dataset, and auto-redeploys on each release.

Patch release: brand palette, job/queue fixes, dependency majors.

  • Burnt/Steel repalette (AA-verified) with the finalised chevron brand mark, the configured site name honoured throughout, and a favicon viewBox fix so the tab icon renders.
  • API docs gained a usable getting-started and clean error documentation, and dropped internal phase codes.
  • Install quickstart fixed. The quickstart’s AA_MASTER_KEY instructions, image path, cosign identity and pgvector setup were corrected.
  • Per-type job concurrency caps are now applied in the single-process worker pool (#278).
  • Saved-search hot loop fixed: the notify coordinator now grid-aligns reschedules instead of spinning (#292).
  • Dependency majors: pdfjs-dist v6 (#308); three.js r185, the dead model-viewer removed, pins moved off latest (#310); supply-chain forks retargeted from mscrnt/* to Artist-Alley-Org (#286).
  • The test suite no longer touches the shared development database (#291).

Patch release fixing the background-job processing outage from v0.1.0, plus release-pipeline and dependency hygiene.

  • Dependency security cleanup: bumped every open advisory in the shipped artifact (golang.org/x/net, DOMPurify) and the optional CLIP sidecar (torch, Pillow, python-multipart), clearing all open Dependabot alerts (#281, #283, #284).
  • Media processing restored: the in-process worker pool never claimed jobs on a fresh install, so thumbnails, previews, transcripts, and search embeddings never generated. Fixed (#279).
  • Release image publishing fixed: the org rename left the container-image owner with capitals, which is an invalid lowercase-only OCI tag; edge and release image builds failed. Corrected (#280).

Docker-only, multi-arch (amd64 + arm64), Sigstore-signed.

The first-ever public release: the transition from pre-tag development to a versioned baseline (RS-derived code removed, AGPL-3.0 relicense, core feature set in place).

Pulled from the roadmap’s Shipped foundation set and checked against the code at the v0.1.0 tag:

  • Single-binary deploy. One Go server with the SvelteKit SPA embedded via go:embed; Postgres + a storage volume (filesystem or any S3-compatible bucket: AWS / R2 / B2 / MinIO). Goose migrations run on boot.
  • Identity & auth. Sessions, API tokens, roles & capabilities, and password policy. An API token carried its account’s own capabilities: scopes could be recorded on a token but were not enforced, and one token per account is now the plan (#1107). An admin screen for configuring single sign-on providers (LDAP, SAML, OAuth) existed, but none of them could sign anyone in, and single sign-on is not available yet; generic SSO is planned for v0.17.0 (ADR 0066).
  • Upload → posts → collections. Drag-anywhere upload with a background queue, per-row tags + per-asset metadata, three post-composition modes, and separate cover thumbnails. Posts wrap assets; collections wrap posts; full-text search spans all of it.
  • Admin-extensible metadata. Operators define typed custom fields for asset types and for collections (a collection field applies to all collections), with audit history (ADR 0012). Each field can name a read and a write capability; the write capability was enforced from this release, while the read capability on asset fields was not enforced until v0.11.0.
  • Browse & review. Grid / masonry / thumbnail / list feeds with a sortable spreadsheet view, and a post detail modal with a multi-asset scroller, comments and likes. Zoom, pan and tile lived in the shared asset viewer; the separate review page was still a placeholder.
  • Universal asset viewer. The universal asset viewer is one Svelte shell hosting per-kind bodies (image, video, audio, PDF, font, 3D) over a shared anchor model, with universal pan/zoom, fullscreen, and jump-to-frame.
  • Format coverage. Images (PNG / JPEG / WebP + HDR / EXR / Radiance), HLS video with frame-accurate scrubbing, audio waveforms, multi-page PDF, font specimens, and 3D viewers for glTF / GLB / OBJ / FBX, plus .mview files through Marmoset’s hosted viewer script. The release image did not include Blender, so 3D turntable previews did not reach published images until v0.5.1.
  • Federation (ArchivePub). Instances could pair with each other over ArchivePub, the walled-garden federation protocol built on the ActivityPub data model, with instance-level Ed25519 HTTP signatures on activity inbox requests, an instance inbox, a delivery worker and admin views of the delivery queues (ADR 0043). The embedded per-actor envelope signatures were placeholders, not cryptographically generated or verified. The encrypted-federation work was complete and the protocol spec stood at v1.0-rc1. No user action crossed instances in this release: liking, commenting on or sharing work between instances was not yet working.
  • Federation keys. Each account could rotate its own federation keys from its security settings. An administrator could rotate another user’s federation keys, and a federation key-health page reported accounts missing encryption keys, peers without negotiated capabilities and retained keys near expiry.
  • Admin & account shells. A 13-section admin menu, shown only to accounts holding system.admin, with real config surfaces (site, SMTP, auth, AI providers, appearance); the API explorer tile was a placeholder, and the server began serving the API reference in v0.2.0. An account shell with profile, theme + language preferences, and API-token management.
  • Theme & i18n. M3-shaped light + dark palettes with admin-configurable font slots; per-user language preference with English shipped and Spanish + French stubs in the picker.
  • License. The source was relicensed from BSD-3 to AGPL-3.0-only ahead of the tag (ADR 0016); the licensing document of the time also described a separate commercial license, but no commercial license was offered, and commercial licensing remains planned.