mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-05 06:59: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>
92 lines
3.1 KiB
Plaintext
92 lines
3.1 KiB
Plaintext
---
|
|
title: "Update Crew"
|
|
description: "Updating a Crew on CrewAI AMP"
|
|
icon: "pencil"
|
|
mode: "wide"
|
|
---
|
|
|
|
<Note>
|
|
After deploying your crew to CrewAI AMP, you may need to make updates to the
|
|
code, security settings, or configuration. This guide explains how to perform
|
|
these common update operations.
|
|
</Note>
|
|
|
|
## Why Update Your Crew?
|
|
|
|
CrewAI won't automatically pick up GitHub updates by default, so you'll need to manually trigger updates, unless you checked the `Auto-update` option when deploying your crew.
|
|
|
|
There are several reasons you might want to update your crew deployment:
|
|
|
|
- You want to update the code with a latest commit you pushed to GitHub
|
|
- You want to reset the bearer token for security reasons
|
|
- You want to update environment variables
|
|
|
|
## 1. Updating Your Crew Code for a Latest Commit
|
|
|
|
When you've pushed new commits to your GitHub repository and want to update your deployment:
|
|
|
|
1. Navigate to your crew in the CrewAI AMP platform
|
|
2. Click on the `Re-deploy` button on your crew details page
|
|
|
|
<Frame></Frame>
|
|
|
|
This will trigger an update that you can track using the progress bar. The system will pull the latest code from your repository and rebuild your deployment.
|
|
|
|
## 2. Resetting Bearer Token
|
|
|
|
If you need to generate a new bearer token (for example, if you suspect the current token might have been compromised):
|
|
|
|
1. Navigate to your crew in the CrewAI AMP platform
|
|
2. Find the `Bearer Token` section
|
|
3. Click the `Reset` button next to your current token
|
|
|
|
<Frame></Frame>
|
|
|
|
<Warning>
|
|
Resetting your bearer token will invalidate the previous token immediately.
|
|
Make sure to update any applications or scripts that are using the old token.
|
|
</Warning>
|
|
|
|
## 3. Updating Environment Variables
|
|
|
|
To update the environment variables for your crew:
|
|
|
|
1. First access the deployment page by clicking on your crew's name
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
2. Locate the `Environment Variables` section (you will need to click the `Settings` icon to access it)
|
|
3. Edit the existing variables or add new ones in the fields provided
|
|
4. Click the `Update` button next to each variable you modify
|
|
|
|
<Frame>
|
|
|
|
</Frame>
|
|
|
|
5. Finally, click the `Update Deployment` button at the bottom of the page to apply the changes
|
|
|
|
<Note>
|
|
Updating environment variables will trigger a new deployment, but this will
|
|
only update the environment configuration and not the code itself.
|
|
</Note>
|
|
|
|
## After Updating
|
|
|
|
After performing any update:
|
|
|
|
1. The system will rebuild and redeploy your crew
|
|
2. You can monitor the deployment progress in real-time
|
|
3. Once complete, test your crew to ensure the changes are working as expected
|
|
|
|
<Tip>
|
|
If you encounter any issues after updating, you can view deployment logs in
|
|
the platform or contact support for assistance.
|
|
</Tip>
|
|
|
|
<Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
|
|
Contact our support team for assistance with updating your crew or
|
|
troubleshooting deployment issues.
|
|
</Card>
|