Release Notes

This page explains how BaseQR release information is organized and how to use it to plan, test, and communicate changes with your team.

Purpose

• Surface product updates in a concise, consistent format.

• Indicate whether action or re-testing is recommended.

• Provide links to affected documentation for faster adoption.

Where to find release notes

• Release notes are published on the Release Notes page (link placeholder).

• Entries are listed in reverse chronological order.

Entry structure

Each entry includes:

• Date — UTC date of release.

• Category — New, Improvement, Fix, or Deprecation.

• Area — UI, QR creation, Dynamic Destinations, Bulk import, Reports/Analytics, API, Auth/Billing, or Security.

• Details — Brief description of the change.

• Impact — None, Low (optional re-test), Moderate (review settings/flows), or High (action required).

• Docs — Links to affected pages.

Impact guidance

• None — No user action expected.

• Low — Optional validation (for example, spot-check exports or a single scan test).

• Moderate — Review settings or processes (for example, confirm UTM handling after a redirect update).

• High — Action required (for example, update an API parameter or re-export assets). Affected docs will be linked.

Common categories

• New — Added capabilities (for example, additional export format).

• Improvement — Usability, performance, or reliability enhancements.

• Fix — Corrected defects without changing expected behavior.

• Deprecation — Announced removal or replacement of a capability with timelines and alternatives.

Recommended review process

• Triage — Scan new entries weekly and identify items marked Moderate or High.

• Assign — Route entries to the appropriate owner (for example, campaign operations, analytics, or API integration).

• Validate — For entries impacting active campaigns, run a quick scan test and confirm GA4 alignment as needed.

• Record — Note any required internal process updates (for example, bulk template version) and share with the team.

Known issues

• If an entry references a known issue, follow the included mitigation steps and monitor the Uptime Status page for updates.

Archive and search

• Older entries remain available for reference. Use search by Area or keyword (for example, “bulk import template”) to retrieve relevant history.