mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-02 05:38:12 +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>
60 lines
2.3 KiB
Plaintext
60 lines
2.3 KiB
Plaintext
---
|
|
title: "개요"
|
|
description: "워크플로우를 자동화하고 외부 플랫폼 및 서비스와 통합합니다"
|
|
icon: "face-smile"
|
|
mode: "wide"
|
|
---
|
|
|
|
이러한 도구들은 에이전트가 워크플로를 자동화하고, 외부 플랫폼과 통합하며, 다양한 서드파티 서비스와 연동하여 기능을 향상시킬 수 있도록 합니다.
|
|
|
|
## **사용 가능한 도구**
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Apify Actor Tool" icon="spider" href="/ko/tools/automation/apifyactorstool">
|
|
웹 스크래핑 및 자동화 작업을 위해 Apify actor를 실행합니다.
|
|
</Card>
|
|
|
|
<Card title="Composio Tool" icon="puzzle-piece" href="/ko/tools/automation/composiotool">
|
|
Composio를 통해 수백 개의 앱 및 서비스와 통합합니다.
|
|
</Card>
|
|
|
|
<Card title="Multion Tool" icon="window-restore" href="/ko/tools/automation/multiontool">
|
|
브라우저 상호작용과 웹 기반 워크플로우를 자동화합니다.
|
|
</Card>
|
|
|
|
<Card title="Zapier Actions Adapter" icon="bolt" href="/ko/tools/automation/zapieractionstool">
|
|
수천 개의 앱을 자동화할 수 있도록 Zapier Actions를 CrewAI 도구로 제공합니다.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## **일반적인 사용 사례**
|
|
|
|
- **워크플로 자동화**: 반복적인 작업과 프로세스 자동화
|
|
- **API 통합**: 외부 API 및 서비스와 연동
|
|
- **데이터 동기화**: 다양한 플랫폼 간 데이터 동기화
|
|
- **프로세스 오케스트레이션**: 복잡한 다단계 워크플로의 조정
|
|
- **서드파티 서비스**: 외부 도구 및 플랫폼 활용
|
|
|
|
```python
|
|
from crewai_tools import ApifyActorTool, ComposioTool, MultiOnTool
|
|
|
|
# Create automation tools
|
|
apify_automation = ApifyActorTool()
|
|
platform_integration = ComposioTool()
|
|
browser_automation = MultiOnTool()
|
|
|
|
# Add to your agent
|
|
agent = Agent(
|
|
role="Automation Specialist",
|
|
tools=[apify_automation, platform_integration, browser_automation],
|
|
goal="Automate workflows and integrate systems"
|
|
)
|
|
```
|
|
|
|
## **통합 이점**
|
|
|
|
- **효율성**: 자동화를 통해 수작업을 줄임
|
|
- **확장성**: 증가하는 작업량을 자동으로 처리
|
|
- **신뢰성**: 워크플로우의 일관된 실행
|
|
- **연결성**: 다양한 시스템과 플랫폼을 연결
|
|
- **생산성**: 자동화가 반복 작업을 처리하는 동안 고부가가치 업무에 집중 |