Skip to main content

Update PastePrompt

PastePrompt releases may be distributed through manual DMG downloads, and some builds may expose configured update checks inside the app. Read release notes before updating during active audit work.

Manual updates​

Use manual updates when you install from the Download page.

  1. Open the Download page.
  2. Read the Release Notes and the latest v0.1.0 note if you are installing the release build.
  3. Download the new DMG for your Mac.
  4. Verify the SHA256 checksum.
  5. Quit PastePrompt.
  6. Open the DMG.
  7. Drag PastePrompt to Applications and replace the existing app.
  8. Launch PastePrompt.
  9. Confirm the version in the app.
  10. Confirm your license status if you use paid features.
Update between review sessions

When possible, update between audits or review sessions. Keep exported bundles and important templates backed up before replacing a working release build.

Auto-updates and update checks​

If your build includes configured update checks, the app may show a settings area such as Settings -> Updates with:

  • Current version.
  • Stable or release channel.
  • Manual check for updates.
  • Auto-check preference.
  • Release notes before install.

If updater support is not configured for your build, use the manual DMG flow.

Release streams​

PastePrompt may publish separate release streams:

  • Current: the latest public release listed on the Download page.
  • Stable: a future lower-change public release stream once multiple release lines exist.

Do not switch release streams in the middle of a time-sensitive review unless you have a reason to accept the risk of workflow changes.

Release notes​

Read release notes for:

  • Install requirements.
  • Signing and notarization status.
  • License behavior changes.
  • New Pro or Founder features.
  • Known issues.
  • Migration notes for settings, workspaces, templates, or history.

The public Changelog lists the latest release, previous release history, channel labels, and published downloads. Individual release-note pages, such as v0.1.0, contain the detailed artifact checklist.

Privacy of update checks​

Configured update checks should only need release metadata such as app version, platform, architecture, and selected channel. They should not send source code, repository contents, prompts, generated bundles, workspace selections, or secret scanner findings.

External network policy

Update checks are separate from context generation. If you are working under a strict no-network audit policy, use manual downloads approved by your environment and disable automatic checks if the app exposes that setting.