Skip to content

BUS Core v1.4.1

Latest
Latest

Choose a tag to compare

View all tags
@truegoodcraft truegoodcraft released this 03 Aug 17:58
Immutable release. Only release title and notes can be modified.
v1.4.1
4cb1f40

BUS Core 1.4.1 is a maintenance release focused on trustworthy update checks, privacy-bounded product telemetry, and safer Windows release artifacts.

This release does not add a new product domain or expand the information BUS Core sends.

Telemetry and product signals

BUS Core’s optional telemetry client now has clearer delivery guarantees and a smaller privacy boundary:

  • An event is considered delivered only after Lighthouse acknowledges its exact event ID.
  • One-time milestones are completed locally only after that acknowledgement.
  • Rejected or retry-exhausted events are retained in a bounded local dead-letter file for diagnostics.
  • Delivery status exposes only aggregate local diagnostics such as pending, acknowledged, rejected, dead-lettered, last-success, and error category.
  • Telemetry remains disabled until the first-run disclosure is acknowledged with telemetry enabled.
  • Disabling telemetry clears the unsent queue.
  • Telemetry failure never blocks local operation.

Outbound telemetry contains only:

  • Event ID and allowlisted event name
  • Client timestamp
  • BUS Core version
  • Release channel
  • Coarse operating-system category

It does not contain a persistent installation identifier, hardware fingerprint, username, filepath, database content, customer or supplier data, items, recipes, invoices, quantities, financial values, documents, or other business content.

Signals included

Product evidence is limited to:

  • First successful launch
  • Once-per-version release adoption
  • Startup and manual update-check outcomes
  • Successful verified update staging
  • Reliability events
  • One-time successful use of major areas:
    • Inventory and stock
    • Contacts
    • Recipes
    • Manufacturing
    • Jobs
    • Invoicing
    • Finance
    • Backup export

BUS Core does not report module opens, active days, sessions, returning installations, engagement, retention, or cross-day behavioral profiles.

The compatible Lighthouse 1.27.0 receiver and server-side migration 0015 were deployed and production-verified before this client release.

Update-check improvements

  • The sidebar startup controller is now the single owner of automatic update checks.
  • Removed the duplicate automatic request previously initiated by Home.
  • Startup checks respect both updates.enabled and updates.check_on_startup.
  • Manual checks remain available even when automatic checks are disabled.
  • Automatic checks are deduplicated to at most one per application launch.
  • Responses now identify the check source, whether a check was performed, and why it may have been skipped.
  • Update-check requests remain limited to the current version, release channel, and aggregate-safe first-check state.
  • BUS Core still does not silently download, install, or restart itself.

Release and artifact integrity

The Windows release pipeline now fails closed when an artifact is incomplete or cannot be verified:

  • Build and runtime dependencies must be present.
  • The governed Python 3.11 and PyInstaller toolchain is enforced.
  • Any non-zero PyInstaller result stops the release.
  • The complete PyInstaller onefile CArchive is verified before copying, signing, or bundling.
  • Unsigned and signed executable launch smoke tests are required.
  • Authenticode signer identity and certificate thumbprint are verified.
  • Artifact hashes are checked after copying.
  • The final ZIP structure and embedded runtime are verified.

Upgrade notes

No BUS Core database migration or manual configuration change is required for this release.

Assets 4
Loading