Skip to documentation content

Release Notes

Product 1.0 RC known issues

Keep accepted Product 1.0 RC caveats, recovery boundaries and missing evidence visible before publication.

This list is intentionally visible because Product 1.0 is a release candidate, not a stable launch. The last known-good package pair is Free 3.28.0-rc.7, Pro 1.36.0-rc.7 and Aurelia 1.1.0-rc.8; do not substitute an untracked ZIP or reuse a version label for different bytes.

External iCal blocks may be delayed until the next scheduler interval. A failed fetch, parse, license or storage operation must preserve the last known-good snapshot and keep its external blocks enforced; it must not silently release occupancy. Check iCal health, UTC timestamps and the source error log before forcing a retry. The existing Booking.com and Agoda API channel remains a separate Advanced Integration and follows its own callback and credential diagnostics.

WooCommerce checkout can be blocked by currency, number-of-decimals or strict order mismatch. Compare the server order and payment ledger rather than browser totals. A single_language provider state is valid and should render a stable label, while a missing evidence state means the report cannot yet support a product-defect claim. Theme cache or stale responsive assets require a real HTTP check after cache invalidation. Escalate with redacted logs, versions, route, locale, viewport and UTC time; never attach credentials, live iCal URLs, payment secrets or production database dumps. These are operational caveats, not permission to bypass the launch gate.

Was this article helpful?

Your feedback helps us improve the documentation.