mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-04 22:49:23 +00:00
a237ebabba
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
113 lines
3.5 KiB
Plaintext
113 lines
3.5 KiB
Plaintext
---
|
|
title: أداة بحث Linkup
|
|
description: أداة `LinkupSearchTool` تتيح الاستعلام من Linkup API للحصول على معلومات سياقية.
|
|
icon: link
|
|
mode: "wide"
|
|
---
|
|
|
|
# `LinkupSearchTool`
|
|
|
|
## الوصف
|
|
|
|
توفر أداة `LinkupSearchTool` القدرة على الاستعلام من Linkup API للحصول على معلومات سياقية واسترجاع نتائج منظمة. هذه الأداة مثالية لإثراء سير العمل بمعلومات محدّثة وموثوقة من Linkup، مما يسمح للوكلاء بالوصول إلى بيانات ذات صلة أثناء مهامهم.
|
|
|
|
## التثبيت
|
|
|
|
لاستخدام هذه الأداة، تحتاج إلى تثبيت Linkup SDK:
|
|
|
|
```shell
|
|
uv add linkup-sdk
|
|
```
|
|
|
|
## خطوات البدء
|
|
|
|
لاستخدام `LinkupSearchTool` بفعالية، اتبع هذه الخطوات:
|
|
|
|
1. **مفتاح API**: احصل على مفتاح Linkup API.
|
|
2. **إعداد البيئة**: قم بإعداد بيئتك بمفتاح API.
|
|
3. **تثبيت SDK**: ثبّت Linkup SDK باستخدام الأمر أعلاه.
|
|
|
|
## مثال
|
|
|
|
يوضح المثال التالي كيفية تهيئة الأداة واستخدامها مع وكيل:
|
|
|
|
```python Code
|
|
from crewai_tools import LinkupSearchTool
|
|
from crewai import Agent
|
|
import os
|
|
|
|
# Initialize the tool with your API key
|
|
linkup_tool = LinkupSearchTool(api_key=os.getenv("LINKUP_API_KEY"))
|
|
|
|
# Define an agent that uses the tool
|
|
@agent
|
|
def researcher(self) -> Agent:
|
|
'''
|
|
This agent uses the LinkupSearchTool to retrieve contextual information
|
|
from the Linkup API.
|
|
'''
|
|
return Agent(
|
|
config=self.agents_config["researcher"],
|
|
tools=[linkup_tool]
|
|
)
|
|
```
|
|
|
|
## المعاملات
|
|
|
|
تقبل أداة `LinkupSearchTool` المعاملات التالية:
|
|
|
|
### معاملات المُنشئ
|
|
- **api_key**: مطلوب. مفتاح Linkup API الخاص بك.
|
|
|
|
### معاملات التشغيل
|
|
- **query**: مطلوب. مصطلح أو عبارة البحث.
|
|
- **depth**: اختياري. عمق البحث. الافتراضي هو "standard".
|
|
- **output_type**: اختياري. نوع المخرجات. الافتراضي هو "searchResults".
|
|
|
|
## الاستخدام المتقدم
|
|
|
|
يمكنك تخصيص معاملات البحث للحصول على نتائج أكثر تحديداً:
|
|
|
|
```python Code
|
|
# Perform a search with custom parameters
|
|
results = linkup_tool.run(
|
|
query="Women Nobel Prize Physics",
|
|
depth="deep",
|
|
output_type="searchResults"
|
|
)
|
|
```
|
|
|
|
## تنسيق الإرجاع
|
|
|
|
تُرجع الأداة النتائج بالتنسيق التالي:
|
|
|
|
```json
|
|
{
|
|
"success": true,
|
|
"results": [
|
|
{
|
|
"name": "Result Title",
|
|
"url": "https://example.com/result",
|
|
"content": "Content of the result..."
|
|
},
|
|
// Additional results...
|
|
]
|
|
}
|
|
```
|
|
|
|
في حالة حدوث خطأ، ستكون الاستجابة:
|
|
|
|
```json
|
|
{
|
|
"success": false,
|
|
"error": "Error message"
|
|
}
|
|
```
|
|
|
|
## معالجة الأخطاء
|
|
|
|
تتعامل الأداة بسلاسة مع أخطاء API وتوفر ملاحظات منظمة. إذا فشل طلب API، ستُرجع الأداة قاموساً يحتوي على `success: false` ورسالة خطأ.
|
|
|
|
## الخلاصة
|
|
|
|
توفر أداة `LinkupSearchTool` طريقة سلسة لدمج قدرات استرجاع المعلومات السياقية من Linkup في وكلاء CrewAI. من خلال الاستفادة من هذه الأداة، يمكن للوكلاء الوصول إلى معلومات ذات صلة ومحدّثة لتعزيز اتخاذ القرارات وتنفيذ المهام. |