Support policy

Pulsar documentation currently covers the root-current 0.4.1 line and links package defects to the

package issue tracker. This is a documentation boundary, not an uncommitted

response-time, compatibility, or backport promise.

Before opening an issue

1. Check troubleshooting and the release-specific upgrade notes.
2. Include the Pulsar and Laravel versions, PHP version, command, normalized output, a minimal reproduction, and only relevant files.
3. Remove secrets, tokens, credentials, tenant identifiers, customer data, and production logs before submitting.

Package-owned intake status

The core repository owns its issue form or template. At the synchronized core revision, no issue form/template is committed under .github; therefore the required structured intake has not been verified. A core maintainer must enable or review an intake that collects the listed reproducibility fields and explicitly prohibits sensitive data. This site link does not replace that core-owned control.

FAQ

Can I submit application architecture requests? The tracker is for reproducible package or documentation defects. This site does not promise application-specific design support.