chore(source-linear): update stale external documentation URLs in metadata

[devin-ai-integration]

What

Found during an API deprecation audit of the Linear API family: every externalDocumentationUrls deep link for source-linear is stale. Linear moved its developer docs off developers.linear.app, and those deep links now 301 to the generic https://linear.app/developers landing page, so deprecation monitoring reads a content-free page. status.linear.app likewise redirects to linearstatus.com.

Resolves https://github.com/airbytehq/oncall/issues/10398

• https://github.com/airbytehq/oncall/issues/10398

How

Repoint the three stale URLs at their current equivalents, add the two docs pages that actually carry deprecation signal, and drop the status-page redirect hop:

type	before	after
api_reference	developers.linear.app/docs/graphql/working-with-the-graphql-api	linear.app/developers/graphql
authentication_guide	developers.linear.app/docs/oauth/authentication	linear.app/developers/oauth-2-0-authentication
rate_limits	developers.linear.app/docs/graphql/...#rate-limiting	linear.app/developers/rate-limiting
api_deprecations	(none)	linear.app/developers/deprecations
api_release_history	(none)	linear.app/changelog
status_page	status.linear.app/	linearstatus.com/

All six were verified to return HTTP 200 with no redirect.

Review guide

1. airbyte-integrations/connectors/source-linear/metadata.yaml

User Impact

None. Metadata-only documentation links; no connector behavior or spec change, so no version bump.

Can this PR be safely reverted and rolled back?

• YES 💚

Requested by Devin Bot on behalf of Danylo Jablonski, as part of the API Deprecation Monitoring playbook run for the Linear API family.

Link to Devin session: https://app.devin.ai/sessions/9e981d132c4d4d1c82b99bab6b4ca9d5

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[octavia-bot]

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /enable-autopilot-rollouts - Enables autopilot progressive rollouts for the modified connector(s) in the PR, remediating "autopilot rollouts not enabled for {connector-name}" auto-merge blockers. Sets defaultRolloutMode: autopilot and enableProgressiveRollout: true, preserving any existing autopilotConfig.
    • Optional args: connector=<CONNECTOR_NAME> (defaults to the modified connectors in the PR), strategy=fast|slow|default (defaults to fast).
    • Example: /enable-autopilot-rollouts or /enable-autopilot-rollouts connector=source-faker strategy=slow
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Note

Autopilot progressive rollouts are not enabled for the following modified connector(s):

• source-linear

This is a courtesy heads-up only — it does not block merge or fail any check.
To enable automatic progressive rollouts for the connector(s) above, comment
/enable-autopilot-rollouts on this PR. This sets defaultRolloutMode: autopilot
and enableProgressiveRollout: true in each connector's metadata.yaml,
preserving any existing autopilotConfig.

[devin-ai-integration]

Note on CI: source-linear Pre-Release Checks fails only on the Connector Version Increment Check ("The dockerImageTag in metadata.yaml was not incremented... Ignore this message if you do not intend to re-release the connector."). This PR only edits externalDocumentationUrls, so no re-release is intended and no version bump is included. Metadata validation and the changelog check both pass in that same job.

This matches the precedent for the same class of change, e.g. #82265 (source-github external docs URL fix), which was merged on 2026-07-30 without a version bump.

Happy to bump dockerImageTag to 0.2.12 with a changelog entry if maintainers would rather have these URLs published with a re-release.

---

Devin session

[github-actions]

source-linear Connector Test Results

49 tests   47 ✅  7s ⏱️
 2 suites   2 💤
 2 files     0 ❌

Results for commit b1b8445.