Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ name = "dimos"
authors = [
{name = "Dimensional Team", email = "build@dimensionalOS.com"},
]
version = "0.0.4"
version = "0.0.7"
Copy link
Contributor

Choose a reason for hiding this comment

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

The version is being bumped from 0.0.4 to 0.0.7, skipping 0.0.6. While git history shows v0.0.5 exists as a tag, there's no v0.0.6 tag or commit. This creates a gap in the version history.

Additionally, uv.lock still references version 0.0.4 for the dimos package and needs to be synchronized with this version change. When the package version in pyproject.toml is updated, the lock file should be regenerated using uv lock to ensure consistency.

Consider:

  1. Either use version 0.0.6 instead (following sequential versioning), or document why 0.0.6 was skipped
  2. Run uv lock to update the lock file with the new version

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

description = "Powering agentive generalist robotics"
requires-python = ">=3.10"
readme = "README.md"
Expand Down
2 changes: 1 addition & 1 deletion uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading