mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 21:28:10 +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>
107 lines
4.4 KiB
Plaintext
107 lines
4.4 KiB
Plaintext
---
|
|
title: بحث Google عبر Serper
|
|
description: أداة `SerperDevTool` مصممة للبحث في الإنترنت وإرجاع النتائج الأكثر صلة.
|
|
icon: google
|
|
mode: "wide"
|
|
---
|
|
|
|
# `SerperDevTool`
|
|
|
|
## الوصف
|
|
|
|
هذه الأداة مصممة لإجراء بحث دلالي عن استعلام محدد من محتوى نصي عبر الإنترنت. تستخدم [serper.dev](https://serper.dev) API
|
|
لجلب وعرض نتائج البحث الأكثر صلة بناءً على الاستعلام المقدم من المستخدم.
|
|
|
|
## التثبيت
|
|
|
|
لاستخدام `SerperDevTool` بفعالية، اتبع هذه الخطوات:
|
|
|
|
1. **تثبيت الحزمة**: تأكد من تثبيت حزمة `crewai[tools]` في بيئة Python الخاصة بك.
|
|
2. **الحصول على مفتاح API**: احصل على مفتاح `serper.dev` API على https://serper.dev/ (طبقة مجانية متاحة).
|
|
3. **تكوين البيئة**: خزّن مفتاح API الذي حصلت عليه في متغير بيئة باسم `SERPER_API_KEY` لتسهيل استخدامه بواسطة الأداة.
|
|
|
|
لدمج هذه الأداة في مشروعك، اتبع تعليمات التثبيت أدناه:
|
|
|
|
```shell
|
|
pip install 'crewai[tools]'
|
|
```
|
|
|
|
## مثال
|
|
|
|
يوضح المثال التالي كيفية تهيئة الأداة وتنفيذ بحث باستعلام معين:
|
|
|
|
```python Code
|
|
from crewai_tools import SerperDevTool
|
|
|
|
# Initialize the tool for internet searching capabilities
|
|
tool = SerperDevTool()
|
|
```
|
|
|
|
## المعاملات
|
|
|
|
تأتي أداة `SerperDevTool` مع عدة معاملات تُمرّر إلى API:
|
|
|
|
- **search_url**: نقطة نهاية URL لـ search API. (الافتراضي هو `https://google.serper.dev/search`)
|
|
|
|
- **country**: اختياري. تحديد البلد لنتائج البحث.
|
|
- **location**: اختياري. تحديد الموقع لنتائج البحث.
|
|
- **locale**: اختياري. تحديد اللغة المحلية لنتائج البحث.
|
|
- **n_results**: عدد نتائج البحث المُرجعة. الافتراضي هو `10`.
|
|
|
|
يمكن العثور على قيم `country` و `location` و `locale` و `search_url` في [Serper Playground](https://serper.dev/playground).
|
|
|
|
## مثال مع المعاملات
|
|
|
|
إليك مثالاً يوضح كيفية استخدام الأداة مع معاملات إضافية:
|
|
|
|
```python Code
|
|
from crewai_tools import SerperDevTool
|
|
|
|
tool = SerperDevTool(
|
|
search_url="https://google.serper.dev/scholar",
|
|
n_results=2,
|
|
)
|
|
|
|
print(tool.run(search_query="ChatGPT"))
|
|
|
|
# Using Tool: Search the internet
|
|
|
|
# Search results: Title: Role of chat gpt in public health
|
|
# Link: https://link.springer.com/article/10.1007/s10439-023-03172-7
|
|
# Snippet: … ChatGPT in public health. In this overview, we will examine the potential uses of ChatGPT in
|
|
# ---
|
|
# Title: Potential use of chat gpt in global warming
|
|
# Link: https://link.springer.com/article/10.1007/s10439-023-03171-8
|
|
# Snippet: … as ChatGPT, have the potential to play a critical role in advancing our understanding of climate
|
|
# ---
|
|
|
|
```
|
|
|
|
```python Code
|
|
from crewai_tools import SerperDevTool
|
|
|
|
tool = SerperDevTool(
|
|
country="fr",
|
|
locale="fr",
|
|
location="Paris, Paris, Ile-de-France, France",
|
|
n_results=2,
|
|
)
|
|
|
|
print(tool.run(search_query="Jeux Olympiques"))
|
|
|
|
# Using Tool: Search the internet
|
|
|
|
# Search results: Title: Jeux Olympiques de Paris 2024 - Actualités, calendriers, résultats
|
|
# Link: https://olympics.com/fr/paris-2024
|
|
# Snippet: Quels sont les sports présents aux Jeux Olympiques de Paris 2024 ? · Athlétisme · Aviron · Badminton · Basketball · Basketball 3x3 · Boxe · Breaking · Canoë ...
|
|
# ---
|
|
# Title: Billetterie Officielle de Paris 2024 - Jeux Olympiques et Paralympiques
|
|
# Link: https://tickets.paris2024.org/
|
|
# Snippet: Achetez vos billets exclusivement sur le site officiel de la billetterie de Paris 2024 pour participer au plus grand événement sportif au monde.
|
|
# ---
|
|
```
|
|
|
|
## الخلاصة
|
|
|
|
من خلال دمج `SerperDevTool` في مشاريع Python، يكتسب المستخدمون القدرة على إجراء عمليات بحث فورية وذات صلة عبر الإنترنت مباشرة من تطبيقاتهم.
|
|
تسمح المعاملات المحدّثة بنتائج بحث أكثر تخصيصاً وتوطيناً. من خلال الالتزام بإرشادات الإعداد والاستخدام المقدمة، يصبح دمج هذه الأداة في المشاريع سلساً ومباشراً. |