Rolino fixed changes
Page 8 of 11. Each page contains at most 30 entries so agents and people can read it without a large context load.
- Current
Publishing actions now display their progress labels correctly instead of showing broken character encoding
- Current
LinkedIn readiness now verifies the exact adjusted image that will be uploaded, and 4:5 framing guidance accurately reports crop loss for landscape, square, and portrait images
- Current
Platform image adjustments now reject read-only workspaces before rendering, serialize concurrent replacements without leaking generated files, and preserve explicit content types in local storage
- Current
Calendar events now show consistent shadcn tooltips on hover and keyboard focus instead of browser-native title popups
- Current
LinkedIn image readiness now verifies stored Media Library and uploaded images before publishing instead of incorrectly requiring replacement
- Current
MCP publishing and integration-health descriptions now explicitly include LinkedIn alongside the other supported destinations
- Current
LinkedIn text-only member posts now use the self-serve Share on LinkedIn publishing endpoint, avoiding repeated server errors from the Marketing Posts surface
- Current
LinkedIn connections now accept both standard scope response formats and preserve a safe, actionable callback failure reason for troubleshooting
- Current
Completed posts now replace stale readiness, save, and publish controls with one header status and only the relevant follow-up actions
- Current
The notification panel now grows with its visible notifications and scrolls only after reaching its existing maximum height
- Current
Instagram Crop or fit and readiness actions now reliably open the editor for saved, uploaded, and Media Library images, saving newly selected media into the draft first
- Current
LinkedIn destinations now work through the browser's Publish now, failed-attempt retry, and readiness-preview routes instead of being dropped by legacy four-provider allowlists
- Current
LinkedIn image failures that occur before final post creation can use bounded safe retries, while only uncertain final create outcomes are quarantined as potentially published
- Current
CLI delivery options, MCP output validation, SDK typing, OpenAPI discovery, package guides, and the public Rolino agent skill now share the same strict TikTok-or-LinkedIn contract
- Current
Shared composer captions now respect the strictest selected character limit when a destination still uses the shared fallback
- Current
Partial draft updates now automatically discard provider-specific settings when their TikTok or YouTube destination is removed
- Current
TikTok publishing now clears stale settings review after content changes, validates live creator options at runtime, blocks unavailable requested interactions instead of silently disabling them, and fails closed when video duration cannot be verified
- Current
Package-boundary verification now validates stable release versions after leaving the beta channel
- Current
Stripe subscriptions canceled through the Customer Portal now use one consistent “Cancels” badge with their scheduled end date across workspace billing, a progressively compact top-navigation treatment down to “Ends 9/6” on phones, and Admin reporting even when Stripe supplies `cancel_at` instead of `cancel_at_period_end`
- Current
Production builds now load the landing hero's perspective, glass, orbit, and activity-card styles from a directly owned stylesheet, preventing stale shared CSS from flattening the calendar after deployment
- Current
Light mode now applies before the first browser paint, preventing the landing page from briefly flashing in dark mode during initial load
- Current
Vercel deployments on Next.js 16.3 now use the platform-managed build output while Docker and other self-hosted builds retain the standalone server bundle
- Current
The post-onboarding connection action now avoids stale client navigation state that could show a 404 immediately after a brand was created
- Current
Onboarding connection guidance now uses distinct setup and success icons, while every publishing provider setup error consistently names `INTEGRATION_ENCRYPTION_KEY`
- Current
Impersonation audit records now require Better Auth to return a successful result, preventing rejected requests from creating false successful admin events
- Current
Updated the MCP and Prisma dependency lines to remove the current known npm audit advisories from production and development installations
- Current
Founding-allocation concurrency tests now clean up their isolated database fixtures, making repeated PostgreSQL integration runs reliable
- Current
Finalized Founding places now have database-backed regression coverage proving their number cannot be released or reassigned after payment
- Current
The PostgreSQL integration command now reads a local `.env` file when present while still refusing to fall back to the development database
- Current
Extending a hosted trial now resets its expiry-reminder delivery state so the workspace receives one reminder for the new end date instead of expiring silently