You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b5e5521
Browse filesBrowse the repository at this point in the historyBrowse files
**Important:** Do not create a new package unless there is an issue that has been reviewed and approved by the core team.
429
-
430
-
#### Initial Release (Preview Phase)
431
-
432
-
For the first release of a new connector package:
433
-
434
-
1. Create a new directory under `packages/` (e.g., `packages/my-connector/`)
435
-
2. Add the package to `tool.uv.sources` in the root `pyproject.toml`
436
-
3. Include samples inside the package itself (e.g., `packages/my-connector/samples/`)
437
-
4.**Do NOT** add the package to the `[all]` extra in `packages/core/pyproject.toml`
438
-
5.**Do NOT** create lazy loading in core yet
439
-
440
-
#### Promotion to Stable
441
-
442
-
After the package has been released and gained a measure of confidence:
443
-
444
-
1. Move samples from the package to the root `samples/` folder
445
-
2. Add the package to the `[all]` extra in `packages/core/pyproject.toml`
446
-
3. Create a provider folder in `agent_framework/` with lazy loading `__init__.py`
447
-
448
-
### Versioning and Core Dependency
449
-
450
-
All non-core packages declare a lower bound on `agent-framework-core` (e.g., `"agent-framework-core>=1.0.0b260130"`). Follow these rules when bumping versions:
451
-
452
-
-**Core version changes**: When `agent-framework-core` is updated with breaking or significant changes and its version is bumped, update the `agent-framework-core>=...` lower bound in every other package's `pyproject.toml` to match the new core version.
453
-
-**Non-core version changes**: Non-core packages (connectors, extensions) can have their own versions incremented independently while keeping the existing core lower bound pinned. Only raise the core lower bound if the non-core package actually depends on new core APIs.
454
-
455
-
### External Dependency Version Bounds
456
-
457
-
The guiding principle for external dependencies is to make the range of allowed versions as broad as possible, even if that means we have to do some conditional imports, and other tricks to allow small changes in versions.
458
-
So we use bounded ranges for external package dependencies in `pyproject.toml`:
459
-
460
-
461
-
- For stable dependencies (`>=1.0.0`), use a lower bound at a known-good version and an explicit upper bound that reflects the maximum major version we currently support (for example: `openai>=1.99.0,<3`).
462
-
- For prerelease (`dev`/`a`/`b`/`rc`) dependencies, use a known-good lower bound with a hard upper boundary in the same prerelease line (for example: `azure-ai-projects>=2.0.0b3,<2.0.0b4`).
463
-
- For `<1.0.0` dependencies, use a known-good bounded range with an explicit upper cap. Prefer the broadest validated range the package can actually support: that may be a patch line, a minor line, or multiple minor lines (for example: `a2a-sdk>=0.3.5,<0.4.0`, `fastapi>=0.115.0,<0.136.0`, `uvicorn>=0.30.0,<0.39.0`).
464
-
- For prerelease (`dev`/`a`/`b`/`rc`) dependencies, use a known-good bounded range with a hard upper cap and keep the range only as broad as the package's validation coverage justifies.
465
-
- Prefer keeping support for multiple major versions when practical. This may mean that the upper bound spans multiple major versions when the dependency maintains backward compatibility; if APIs differ between supported majors, version-conditional imports/branches are acceptable to preserve compatibility.
466
-
- When adding or changing an external dependency, first run `uv run poe validate-dependency-bounds-test` to validate workspace-wide lower/upper compatibility, then run `uv run poe validate-dependency-bounds-project --mode both --package <workspace-package-name> --dependency "<dependency-name>"` to expand package-scoped bounds.
426
+
The decision to expose a package through lazy loading, and the namespace to use, is a package-governance decision
427
+
rather than a coding convention. Follow
428
+
[`python-package-management`](.github/skills/python-package-management/SKILL.md) for package creation, lifecycle
0 commit comments