Prepare v0.0.2 release

Author: DavidBabinec

CHANGELOG.md

@@ -6,10 +6,16 @@ This project is pre-1.0. Breaking changes may appear in minor or patch releases
 
 ## Unreleased
 
+## 0.0.2 - 2026-06-09
+
 - Added public repository community files and contribution workflow docs.
 - Tightened forwarded-origin handling so `X-Forwarded-Proto` and `X-Forwarded-Host` are trusted only from configured proxy peers.
+- Added Render deployment blueprints and refreshed public deployment docs.
+- Improved static site import fidelity, including imported runtime behavior and CSS cascade isolation.
+- Added editable HTML attributes and path-derived Site Explorer organization.
+- Hardened plugin media handling, public forms, AI credential storage, and MFA secret encryption.
 
-## 0.0.1 - Pending
+## 0.0.1 - 2026-06-08
 
 - First public preview release.
 - Self-hosted Bun CMS server with SQLite and Postgres support.

README.md

@@ -144,7 +144,7 @@ INSTATIC_IMAGE=ghcr.io/corebunch/instatic:latest docker compose -f compose.prod.
 Pin a version for predictable upgrades:
 
 ```sh
-INSTATIC_IMAGE=ghcr.io/corebunch/instatic:0.0.1 docker compose -f compose.prod.yml -f compose.sqlite.yml up -d
+INSTATIC_IMAGE=ghcr.io/corebunch/instatic:0.0.2 docker compose -f compose.prod.yml -f compose.sqlite.yml up -d
 ```
 
 Use **Postgres** when you have a multi-author editorial team, need horizontal app scale-out, or already operate Postgres:

docs/deployment/README.md

@@ -55,7 +55,7 @@ INSTATIC_IMAGE=ghcr.io/corebunch/instatic:latest docker compose -f compose.prod.
 Pin a semver tag for predictable upgrades:
 
 ```sh
-INSTATIC_IMAGE=ghcr.io/corebunch/instatic:0.0.1 docker compose -f compose.prod.yml -f compose.sqlite.yml up -d
+INSTATIC_IMAGE=ghcr.io/corebunch/instatic:0.0.2 docker compose -f compose.prod.yml -f compose.sqlite.yml up -d
 ```
 
 Source builds remain supported for contributors and release-candidate testing:

docs/deployment/docker-image.md

@@ -35,19 +35,19 @@ GHCR is the canonical image registry:
 
 ```sh
 docker pull ghcr.io/corebunch/instatic:latest
-docker pull ghcr.io/corebunch/instatic:0.0.1
+docker pull ghcr.io/corebunch/instatic:0.0.2
 ```
 
 Docker Hub is a discoverability mirror:
 
 ```sh
 docker pull corebunch/instatic:latest
-docker pull corebunch/instatic:0.0.1
+docker pull corebunch/instatic:0.0.2
 ```
 
 When both registries are available, prefer GHCR in Compose files because it is produced directly by the release workflow.
 
-The v0.0.1 published image is built for `linux/amd64`. Use it on Railway and x86_64 VPS/container hosts. ARM64 hosts should build from source for now, or wait for the native arm64 release job before pulling GHCR images directly.
+The v0.0.2 published image is built for `linux/amd64`. Use it on Railway and x86_64 VPS/container hosts. ARM64 hosts should build from source for now, or wait for the native arm64 release job before pulling GHCR images directly.
 
 ## Run With SQLite
 
@@ -100,7 +100,7 @@ Replace `instatic:local` with `ghcr.io/corebunch/instatic:<tag>` when deploying
 Create an app service from Docker image source:
 
 ```txt
-ghcr.io/corebunch/instatic:0.0.1
+ghcr.io/corebunch/instatic:0.0.2
 ```
 
 Attach a Railway volume at `/app/storage`, set the health check path to `/health`, and set app variables:
@@ -113,7 +113,7 @@ STATIC_DIR=/app/dist
 INSTATIC_SECRET_KEY=<output of bun run scripts/generate-secret-key.ts>
 ```
 
-Enable Railway Image Auto Updates when you want Railway to move the service forward automatically during a maintenance window. Use `:latest` for "always follow the newest image", or a semver tag such as `:0.0.1` if you want Railway's semver update controls.
+Enable Railway Image Auto Updates when you want Railway to move the service forward automatically during a maintenance window. Use `:latest` for "always follow the newest image", or a semver tag such as `:0.0.2` if you want Railway's semver update controls.
 
 ## Run On Render From The Image
 

docs/deployment/railway.md

@@ -16,7 +16,7 @@ Railway is the simplest managed target for Instatic because it can run the publi
 Both templates use:
 
 ```txt
-Image=ghcr.io/corebunch/instatic:0.0.1
+Image=ghcr.io/corebunch/instatic:0.0.2
 PORT=8080
 UPLOADS_DIR=/app/storage/uploads
 STATIC_DIR=/app/dist
@@ -30,7 +30,7 @@ Configure the app service health check path as `/health`. If Railway asks which
 Use a Docker image source for production installs:
 
 ```txt
-ghcr.io/corebunch/instatic:0.0.1
+ghcr.io/corebunch/instatic:0.0.2
 ```
 
 The image already runs:
@@ -46,7 +46,7 @@ Recommended service settings:
 | Setting | Value |
 |---|---|
 | Source | Docker image |
-| Image | `ghcr.io/corebunch/instatic:0.0.1` |
+| Image | `ghcr.io/corebunch/instatic:0.0.2` |
 | Public networking | HTTP enabled |
 | Target port | `8080` |
 | Healthcheck path | `/health` |
@@ -121,7 +121,7 @@ Railway volume backups apply to mounted volumes. For Postgres, use Railway's dat
 Enable Railway Image Auto Updates on the app service:
 
 - Use `ghcr.io/corebunch/instatic:latest` when you want the service to redeploy whenever the `latest` tag moves.
-- Use a semver tag like `ghcr.io/corebunch/instatic:0.0.1` when you want Railway to stage matching patch or minor updates according to the service's auto-update preference.
+- Use a semver tag like `ghcr.io/corebunch/instatic:0.0.2` when you want Railway to stage matching patch or minor updates according to the service's auto-update preference.
 
 Set a maintenance window before enabling automatic updates on sites with attached volumes.
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "instatic",
   "private": true,
-  "version": "0.0.1",
+  "version": "0.0.2",
   "engines": {
     "bun": ">=1.3.0 <1.4.0"
   },