Developer release notes

Read a release record

Every published record identifies the component and semantic version, what changed, its compatibility range, and whether action is required. Informational and recommended releases remain in the dashboard and CLI. BlinkHost may also send an operational email when a confirmed project is affected by a security update, required migration or retirement deadline.

Understand impact labels

• Informational: no action is expected.
• Recommended: upgrading improves capability, reliability or developer experience.
• Action required: an affected project needs a documented change.
• Security: review promptly; the record identifies affected versions without exposing exploit details.
• Retirement: migrate before the stated support deadline.

Release notices show the project, detected component version, evidence source and confidence. A confirmed finding comes from a build manifest, deployed artifact or authenticated CLI session. BlinkHost does not treat a filename guess as confirmed evidence.

Use release notes from the CLI

Run blinkhost update check, blinkhost update notes, or blinkhost update notes VERSION. Automatic checks are cached, never install software, do not interrupt a successful command, and are suppressed in CI, non-interactive terminals and JSON output.