Skip to content

Conversation

@sdreyer
Copy link
Collaborator

@sdreyer sdreyer commented Dec 5, 2025

Rules to update versions of libraries that were changed and any dependencies if there are breaking changes


Note

Adds .cursor/versioning.mdc with rules to bump library versions and dependency minimums on breaking changes.

  • Documentation:
    • Add /.cursor/versioning.mdc with versioning rules:
      • Always bump library version in pyproject.toml when files are updated.
      • Increase minimum required dependency versions when there are breaking changes.

Written by Cursor Bugbot for commit ac4e22b. This will update automatically on new commits. Configure here.

@sdreyer sdreyer requested a review from EricGustin December 5, 2025 21:22
@codecov
Copy link

codecov bot commented Dec 5, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Comment on lines +6 to +7
- ALWAYS increase the version of a library in pyproject.toml when files are updated
- Increase the minimum required version of dependencies if there is a breaking change between dependencies
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- ALWAYS increase the version of a library in pyproject.toml when files are updated
- Increase the minimum required version of dependencies if there is a breaking change between dependencies
# Versioning
This repository contains 5 libraries: arcade-core, arcade-tdk, arcade-serve, arcade-mcp-server, and arcade-mcp (CLI)
## Dependency graph recap:
1. arcade-core
- The base library
2. arcade-tdk
- Depends on: arcade-core
3. arcade-serve
- Depends on: arcade-core
4. arcade-mcp-server
- Depends on: arcade-core, arcade-serve, arcade-tdk
5. arcade-mcp
- Depends on: arcade-mcp-server, arcade-core
- Dev/optional deps: arcade-serve, arcade-tdk
## Rules
- ALWAYS use semver (semantic versioning)
- ALWAYS increase the version of a library in pyproject.toml when a library's code is modified.
- ALWAYS increase the minimum required version of dependencies if there is a breaking change between dependencies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants