Skip to content

[rename] rename, w/ deprecate#6

Merged
asaiacai merged 15 commits into
mainfrom
pluto-rename
Jan 12, 2026
Merged

[rename] rename, w/ deprecate#6
asaiacai merged 15 commits into
mainfrom
pluto-rename

Conversation

@asaiacai

Copy link
Copy Markdown

Tested (run the relevant ones):

  • Code formatting: bash format.sh
  • Any manual or new tests for this PR (please specify below)

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @asaiacai, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request rebrands the MLOps framework's Python client library by renaming its core package from 'mlop' to 'pluto'. This change involves updating all internal references, documentation, and configuration settings to reflect the new name. A key aspect of this transition is the implementation of a backward compatibility layer, ensuring that existing codebases using 'import mlop' will continue to function, albeit with deprecation warnings, facilitating a smooth migration for users.

Highlights

  • Package Rename: The core MLOps client library has been renamed from 'mlop' to 'pluto'.
  • Backward Compatibility: A backward compatibility layer has been implemented, allowing 'import mlop' to still function by internally importing from 'pluto' and issuing a DeprecationWarning.
  • Updated References: All internal code references, documentation (CLAUDE.md, README.md), scripts (format.sh, test_neptune_migration.sh), and tests have been updated to reflect the new 'pluto' name.
  • Environment Variables: Environment variables now use the 'PLUTO_' prefix. Old 'MLOP_' prefixed variables are deprecated but still supported with warnings to aid migration.
  • PyPI Package Name: The PyPI package name has been updated from 'trainy-mlop' to 'pluto-ml' in pyproject.toml.
Ignored Files
  • Ignored by pattern: .github/workflows/** (6)
    • .github/workflows/lint.yml
    • .github/workflows/mlop.yml
    • .github/workflows/mypy.yml
    • .github/workflows/neptune-compat.yml
    • .github/workflows/pypi-publish-nightly.yml
    • .github/workflows/pytest-smoke.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request undertakes a comprehensive renaming of the project from mlop to pluto. The changes are extensive, covering code, documentation, tests, and configuration files. The implementation correctly introduces backward compatibility shims for the old mlop package, ensuring a smooth transition for existing users. The use of deprecation warnings is a good practice. My review focuses on the completeness and consistency of this renaming effort. I've found a few minor inconsistencies that should be addressed to finalize the refactoring.

Comment thread README.md Outdated
Comment thread pluto/__init__.py Outdated
Comment thread pluto/compat/neptune.py Outdated
Ubuntu and others added 11 commits January 12, 2026 11:32
- Update Colab notebook links from mlop-ai/mlop to Trainy-ai/pluto
- Rename _MLOP_COMMIT_SHA to _PLUTO_COMMIT_SHA in pluto/__init__.py
- Fix log message to reference PLUTO_PROJECT instead of MLOP_PROJECT

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Fix F821: rename _MLOP_COMMIT_SHA to _PLUTO_COMMIT_SHA in pluto/__init__.py
- Fix E402: add noqa comments to mlop shim imports (intentional after warnings)
- Fix E501: wrap long lines in pluto/compat/neptune.py and tests/test_env_vars.py

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Update test assertions to use _pluto_run instead of _mlop_run
after the attribute was renamed during the mlop->pluto rebranding.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Using @main can cause instability due to untested changes.
Pin to a stable release version.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The Poetry action cache was restoring virtualenvs without dev
dependencies installed (mypy, pytest). Poetry would skip installation
thinking deps were already present, causing "Command not found" errors.

Fix: Clear .venv before poetry install to force fresh installation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The workflow was referencing `secrets.PLUTO_API_TOKEN` which doesn't
exist in the repo. Changed to use `secrets.MLOP_API_TOKEN` which is
the actual secret name configured in GitHub.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

@asaiacai asaiacai left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

left comments

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Ubuntu and others added 3 commits January 12, 2026 16:32
- Change mlop-ai/server link to docs.trainy.ai/pluto
- Fix documentation URL to docs.trainy.ai/pluto
- Comment out colab tutorial links

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Users can now configure authentication and project via environment
variables instead of only through the Python SDK or CLI:

- PLUTO_API_TOKEN: Sets the API token (alternative to `pluto login`)
- PLUTO_PROJECT: Sets the default project (alternative to `init(project=...)`)

Both support deprecated MLOP_* fallbacks with warnings.

Precedence order: function params > env vars > keyring > defaults

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@asaiacai asaiacai merged commit e7373a6 into main Jan 12, 2026
12 checks passed
@asaiacai asaiacai deleted the pluto-rename branch January 12, 2026 22:00
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.

1 participant