Linearavel Laravel Package

Product Decisions This Supports

• Roadmap sequencing for collaboration features. inlineAnchorFrom / inlineAnchorTo on CommentCreateInput mean the package can create comments anchored to specific text ranges in a document or issue body, not just top-level comments. This turns "inline review comments" from a custom-integration project into a config-level feature — relevant if you are scoping review/annotation workflows this quarter.
• Build vs. buy on the Linear integration layer. 0.2.9 is a pure schema re-sync (rebuilt from the Linear GraphQL schema as of 2026-10-16), including two new workflow triggers and two new document share roles. The vendor is tracking Linear's schema closely; that ongoing maintenance is the thing you would otherwise own. Treat the package as the default and reserve build effort for the delta it does not cover.
• Automation and gating features become reachable. addedToMergeQueue and removedFromMergeQueue on WorkflowTrigger let you subscribe to merge-queue lifecycle events. This supports product decisions around PR gating, release automation, and "who gets notified when a change enters the queue" — features previously requiring polling or webhook shims.
• Permissions model for shared documents. DocumentShareRole now includes view and comment. If you are designing document sharing, you can ship a three-tier model (view / comment / edit) without inventing a parallel permission store, and you avoid over-granting edit rights to reviewers — a real security-review talking point.
• Integration provenance. origin on IntegrationSettingsInput lets you tag which surface created or configured an integration. That supports audit answers like "was this set up by a human in the UI or by our provisioning job?", which matters for enterprise onboarding and support triage.
• Upgrade cadence planning. This release is additive only — optional input fields and new enum members, no removals or renames. It is a low-risk upgrade that does not require a migration window, which is useful evidence when arguing for a routine dependency-refresh policy rather than ad-hoc upgrades.

When to Consider This Package

Adopt when:

• Linear is a system of record for issues, projects, or docs, and you need to write to it from Laravel (creating issues, comments, integrations settings), not just read.
• You want a maintained, schema-derived client rather than hand-written GraphQL queries that drift every time Linear ships — the "as of 2026-10-16" rebuild is the value proposition.
• Your workflows touch code review or release automation and would benefit from merge-queue triggers.
• You can tolerate a 0.x version line. Version 0.2.9 signals pre-1.0; expect the public API around the generated types to keep moving.

Look elsewhere or wait when:

• Your needs are read-only reporting — a thinner HTTP client or direct GraphQL calls may be less surface area to own.
• You require a stable, semver-guaranteed contract with deprecation windows. Additive enum growth is technically backward compatible, but if your code does exhaustive match/switch on WorkflowTrigger or DocumentShareRole, a new case can produce unhandled branches at runtime. Budget for a defensive default arm, or pin the version and upgrade deliberately.
• You need features Linear's public schema does not expose — this package cannot get ahead of the upstream schema.
• You are not on a supported Laravel/PHP version; verify before committing, since an unmaintained compatibility matrix is a common 0.x trap.

How to Pitch It (Stakeholders)

To executives: This is a low-cost dependency that keeps our Linear integration current without engineering upkeep. The latest release (0.2.9) is a routine schema sync that adds optional capabilities — inline comment anchoring, merge-queue automation hooks, finer document sharing permissions, and integration provenance — with no breaking changes and no migration work. It expands what we can ship on top of Linear without expanding headcount.

To engineering: Release 0.2.9 is additive only: optional inlineAnchorFrom / inlineAnchorTo on CommentCreateInput, optional origin on IntegrationSettingsInput, new WorkflowTrigger values (addedToMergeQueue, removedFromMergeQueue), and new DocumentShareRole values (view, comment). Nothing removed, nothing renamed, so the upgrade is low risk. Two caveats to plan for: we are still on a 0.x line, so pin the version and upgrade on a schedule; and any exhaustive enum handling should get a default branch before we consume the new trigger and share-role values.