KitsuSync v0.5.1

KitsuSync v0.5.1

KitsuSync v0.5.1 carries the accepted production-detail, reviewer, notification-delivery, User Linking, visual-system, and staging/provenance improvements on the accepted master commit f8a32bbba94d84068d9e96c18554ac4ab7b24540.

Verification

• Tag CI: https://github.com/ukyovfx/kitsusync/actions/runs/38153083301 — PASS
• Tag-ref Security Audit: https://github.com/ukyovfx/kitsusync/actions/runs/38153098551 — PASS, including CodeQL, Go race, Trivy, vulnerability/static analysis, and deployment shell audit
• Release bundle workflow (deployment_mode=normal): https://github.com/ukyovfx/kitsusync/actions/runs/38153403714 — PASS
• The bundle provenance binds version/tag 0.5.1 / v0.5.1, source and release commit f8a32bbba94d84068d9e96c18554ac4ab7b24540, immutable image identity, Compose, and deployment tools. Runtime reconstruction and recovery/deployment behavior checks passed in the workflow.
• Deployment bundle SHA-256: 66a906d61c0e8d448a86a82b038dc156460980ad3ed7b7adf82a9158ef48369b

Acceptance limitation

Real Discord message and role/user mention delivery E2E was not exercised for this release. No live Discord E2E is claimed.

v0.5.0 history

The immutable v0.5.0 tag remains on its original commit, but its GitHub Release and deployment bundle were never published after the tag-CI provenance-input failure. Its accepted source changes are carried forward in v0.5.1.

KitsuSync v0.4.9

What's Changed

• Fix rollback validation for setup-required recovery by @ukyovfx in #211
• Prepare v0.4.9 hotfix release by @ukyovfx in #212

Full Changelog: v0.4.8...v0.4.9

KitsuSync v0.4.8

What's Changed

• Harden CI action provenance and Go toolchain source by @ukyovfx in #181
• Add initial pre-1.0 security audit workflow by @ukyovfx in #182
• Expand pre-1.0 security audit coverage by @ukyovfx in #183
• Fix admin session resurrection after restart by @ukyovfx in #187
• Avoid ambiguous Discord webhook retries by @ukyovfx in #189
• Harden runtime apt install recommendations by @ukyovfx in #193
• Update x/text to fixed release by @ukyovfx in #194
• ci: enforce clean pre-v1.0 security checks by @ukyovfx in #195
• ui: align Current IA with canonical v1 contract by @ukyovfx in #197
• chore: add Dependabot updates by @ukyovfx in #200
• docs: require evidence-first community debugging by @ukyovfx in #201
• docs: refresh accepted repository state by @ukyovfx in #202
• runtime: use persisted Kitsu credentials for live reads by @ukyovfx in #204
• ui: make Connections token replacement reversible by @ukyovfx in #205
• fix: use persisted Kitsu credentials in Production setup by @ukyovfx in #207
• feat: wire User Linking readiness into Current IA by @ukyovfx in #206
• docs: refresh accepted repository state after runtime scope merges by @ukyovfx in #208
• Prepare v0.4.8 release by @ukyovfx in #209

Full Changelog: v0.4.7...v0.4.8

KitsuSync v0.4.7

What's Changed

• Harden v0.4.6 production bootstrap and deploy bundle by @ukyovfx in #164
• Fix Docker inspect rollback snapshot compatibility by @ukyovfx in #165
• Harden portable Docker image identity by @ukyovfx in #166
• Fix production deployment rollback transaction by @ukyovfx in #167
• Reconcile project state and production verification handoff by @ukyovfx in #168
• Keep downloadable release assets on latest release only by @ukyovfx in #162
• Fix legacy bootstrap detection for recovered containers by @ukyovfx in #169
• Fix bootstrap detector contract harness by @ukyovfx in #170
• Fix inspect detection for recovered legacy container by @ukyovfx in #171
• Fix inspect detector contract assertion by @ukyovfx in #172
• Harden inspect detector contract test by @ukyovfx in #173
• fix: detect recovered legacy runtime during deploy by @ukyovfx in #174
• Support fresh production installation for v0.4.6 by @ukyovfx in #175
• Fix clean-host bootstrap helper installation by @ukyovfx in #176
• Fix fresh install proxy validation topology by @ukyovfx in #177
• Fix fresh bootstrap numeric UID ownership by @ukyovfx in #178
• Fix Zou health check for optional services by @ukyovfx in #179
• Prepare v0.4.7 release by @ukyovfx in #180

Full Changelog: v0.4.6...v0.4.7

KitsuSync v0.4.6

KitsuSync v0.4.6 delivers release-level security and recovery hardening across authentication and session handling, pinned verified Kitsu credential transport, HTTP resource and rate-limit controls, transactional runtime configuration persistence, health/readiness separation, hardened deployment and rollback semantics, immutable source/build/image/runtime provenance, restrictive SQLite/runtime file permissions, and token-first recovery. The production deployment path is consolidated on deploy/kitsusync-deploy, with stale or deprecated recovery/deployment artifacts removed.\n\nF02 (historical AdminSession production persistence proof) remains intentionally deferred. Upgrades must preserve SQLite data, runtime secret material, and operator configuration as one compatible state.

KitsuSync v0.4.5

KitsuSync v0.4.5 hardens Kitsu connectivity, setup, and runtime recovery.

• Hardened Kitsu connection and API routing.
• Preserved external/display URL separation from internal/runtime API targets.
• Added redirect and DNS-rebinding protections for credential delivery.
• Added safe support for explicit trusted private/Tailscale DNS targets.
• Improved runtime credential recovery and validation.
• Preserved encrypted Discord token persistence.
• Runs the container as a non-root user.
• Hardened CSRF and debug exposure protections.
• Improved RC validation with focused security gates.
• Final RC validation passed with FINAL=PASS and 0 reachable govulncheck findings.

KitsuSync v0.4.4

Software RC validated for KitsuSync v0.4.4.

• Finalized Discord notification cards with responsive desktop/mobile layout.
• WFA notifications mention Checkers; RETAKE/DONE notifications mention Assignees with scoped allowed mentions.
• Durable previous-status transitions across polling and restart/recreate.
• External Kitsu URL override with original user-facing URL fallback.
• Clickable Kitsu and Drive deep links, plus durable Storage save feedback.
• Polling/runtime reliability improvements and confirmed dead-code cleanup.
• Security and static validation completed; reachable vulnerabilities: 0.

Production deployment is environment-specific and was not validated by this release.

KitsuSync v0.4.3

KitsuSync v0.4.3

Summary

v0.4.3 fixes Kitsu endpoint selection during fresh initialization. KitsuSync validates safe configured and local candidates before login and provides a secure operator-entered fallback when the supported deployment topology cannot be discovered automatically.

Fixed

• Removed placeholder Kitsu hostname fallback from the login path.
• Preserved the Studio Manager-or-higher login requirement.
• Added bounded, read-only Kitsu API validation for operator-supplied endpoints.

Changed

• Endpoint resolution order is explicit configuration, previously verified saved endpoint, supported local discovery, then validated operator input.
• A manually entered endpoint is persisted only after successful Kitsu authentication.
• Discovery source diagnostics remain safe and never include credentials or tokens.

Upgrade notes

• No database migration is required.
• Preserve existing SQLite data, the runtime secret, and configuration together during upgrade.
• If Kitsu cannot be detected automatically, open /bot/login and enter the Kitsu base URL when prompted. KitsuSync verifies it before use.

Validation

• Focused discovery and login tests pass in the supported CGO-enabled environment.
• Full deployment verification remains topology-dependent when the Kitsu service is host-loopback-only and unreachable from the KitsuSync container.

Environment-specific follow-up

• vfxstudio privileged deployment and end-to-end validation remain pending while the approved breakglass access path is being recovered. This does not block the OSS release; no shared infrastructure changes are included in this release.

KitsuSync v0.4.2

KitsuSync v0.4.2

Summary

v0.4.2 adds compact, status-aware Discord notification cards while preserving the existing Production routing and delivery flow.

Notification cards

• WFA, RETAKE, and DONE show status icons, transition-aware messages, and the current Kitsu Task Status color as the embed accent.
• Task Type remains plain text; the redundant lower Status field is removed.
• WFA mentions the Production-configured Checker, RETAKE mentions the resolved assignee, and DONE does not mention anyone by default.
• User mentions are validated, deduplicated, bounded, and kept in exact agreement with Discord AllowedMentions.
• Comment-only updates use dedicated wording and do not show a fabricated status transition.
• Assignee names, Kitsu links, Google Drive links, and preview images appear only when safely available.
• Long user-provided content is truncated deterministically to remain within Discord limits.

Compatibility and safety

• Existing new-message delivery followed by old-message deletion is unchanged.
• Missing User Linking, assignee, comment, link, preview, or status-color data degrades safely.
• No database migration is required for this release candidate.
• Preserve SQLite data, the runtime secret key, and operator configuration together during upgrade.

Validation

• Focused Discord renderer and recipient tests passed.
• Full Go tests and vet passed in the supported CGO-enabled validation environment.
• Controlled Discord E2E passed using disposable resources only; all disposable resources were removed afterward.

KitsuSync v0.4.1

KitsuSync v0.4.1

Summary

v0.4.1 is a maintenance release for the operator-facing setup and administration flow delivered in v0.4.0. The v0.4.0 tag and history remain unchanged.

Changes

• Documentation and version metadata identify this release as v0.4.1.
• The public setup guide matches the current seven-step Production connection flow.
• The documentation asset cache key is refreshed so updated guidance is loaded after deployment.
• The existing KitsuSync UI, Discord routing behavior, and stored data model are unchanged from v0.4.0.

Validation

• Focused documentation route tests passed.
• The v0.4.1 candidate was built from a clean clone and /health returned HTTP 200.
• The existing v0.4.0 tag was preserved and no tag or GitHub Release was created.

Upgrade Notes

No database migration is required for v0.4.1. Preserve the existing SQLite data, runtime secret key, and operator configuration together during upgrade.