Skip to main content

Update Checks

PastePrompt releases can be distributed through manual downloads, and some builds may include configured update checks. Update behavior depends on the release channel and build configuration.

Update channels​

PastePrompt may use release channels such as:

  • Stable: intended for users who want fewer changes during active work.
  • Current: intended for users who want the latest public release and are comfortable with faster iteration.

Read release notes before switching channels or updating during a client review.

What an update check may contact​

If update checks are configured, the app may contact a static release manifest, update server, or release endpoint for the selected channel. A check may need metadata such as:

  • Current app version.
  • Platform.
  • CPU architecture.
  • Selected update channel.
  • Release manifest URL.

An update check should not need repository contents, selected file paths, prompt text, generated bundles, workspace names, secret scanner findings, or Git diffs.

Source-code privacy​

Update checks should be separate from repository analysis. PastePrompt does not need to send source code to determine whether a newer app version exists.

If you work in an environment with strict network controls, use manual downloads from an approved machine or disable update checks if the build provides that setting.

Release signatures and checksums​

Release integrity can involve several concepts:

  • Checksum: a published SHA256 value lets you verify that the downloaded file matches the release artifact.
  • Code signing: a signed macOS app lets Gatekeeper identify the developer identity used to sign the build.
  • Notarization: Apple notarization indicates Apple processed the signed artifact for malware scanning and Gatekeeper compatibility.

Only rely on signing and notarization claims for a specific release when the Download page or release notes state that the artifact is signed and notarized. Some release artifacts may have additional macOS prompts when signing or notarization is not configured.

Manual update workflow​

  1. Read the release notes.
  2. Download the correct macOS artifact for your CPU architecture.
  3. Verify the SHA256 checksum when provided.
  4. Quit PastePrompt.
  5. Replace the installed app from the DMG.
  6. Launch PastePrompt and confirm the version.
  7. Check that workspaces, templates, and license status still look correct.