Merging main into metrics #183
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added server name to the readme file for mcp registry publishing
added workflow dispatch to the publish github action
Updated version number in the hotfix
* Auto-generated server.json * Merged main changes on version/README * Auto-generated server.json * Added workflow_dispatch * Added separate workflows * Remove trigger on tag
* Modified mcp-publisher to use latest release
* Fallback for duplicate push on MCP Registry
* Removed unified publish workflow
* hotfix/2.1.6
* Manual fixes to workflows * Changes to publish.yml * Removed branch restriction on publish mcp * Removed branch restriction on download metrics --------- Co-authored-by: Rohit John Varghese <[email protected]>
* update the paths in the examples appropriately * Fix: Removed Optional for IP and PORT in connect_to_robot. This sometimes generates truncation, no need for optional as they are intrinsically optional. * Added ip and port information on config yaml file * Added turtlesim.yaml * ruff format fix * Added configuration file for local_rosbridge.yaml * trigger ruff check * Revert "Added ip and port information on config yaml file" This reverts commit 131fae4. * Removed ip/port * Add ROS 2 Parameters API (#135) * Added get_parameters set_param get_param etc. Inspect parameters missing. * Fixed inspect_all_parameters. Now tested with background color of turtlesim. * Fixed parameter type in inspect_all_parameters + added get_parameter_details * Added note that parameters are supported on ROS 2 only * Added get_actions tool * Added get_action_type tool * Added get_action_details and inspect_all_actions tools * Added send_action_goal, non-blocking, no feedback or result. * Fixed send_action_goal to: - Be blocking and waiting for action_result or timeout. - Return action_result when action is completed. - Return the last action_feedback, if available, when timeout. - Return timeout/success:false if no action_feedback or action_result is detected. - Fixed bug with timeout input tools (no Optional) * Added cancel_action_goal. Non-blocking. No response is available. Tested with fibonacci server. * Added note for ROS 2 support only. * Added get_action_status tool * Modified get_action_status to work with action_name and not action_type * Added action_feedback through ctx.report_progress. Tested and working in Cursor, not showing in ChatGPT. * Refactor: replace Optional with union syntax (Type | None) (#143) - Remove Optional imports and usage - Update server.py and websocket_manager.py * Add ROS 2 Launch System (#138) * Created ROS2 launch files for rosbridge and turtlesim demo, removed manual launch_ros.sh + Added docs on launch system * Modified documentation * Improved launch_mcp_tunnel to include default options for port and domain. * Moved robot specifications folder to root * updated Manifest and pyproject to point to correct locations * Type hint fix in server.py from previous PR on ros actions * updated config_utils to access specification files using Path * updated tool names and descriptions for getting robot spec * updated name of get verified robots list based on issue feedback * Fixed inconsistent tool names of topic subscribers and publishers, solving #141 * Modify WSL installation documents (#169) docs: add WSL path best practices to prevent common issues - Add warnings to recommend using /home/username/ instead of /mnt/c/Users/username/ - Fix incorrect path labeling - Add explanatory comment to config/mcp.json template - Closes #102 * Cleared naming convention and removed optional scaffolding to state spec file directory explicitly (YAGNI principle) * changed print statements from stdout to stderr for errors * ruff * Bump version to v2.1.7 * Update version to v2.1.7 in server.json and uv.lock --------- Co-authored-by: Jungsoo Lee <[email protected]> Co-authored-by: Stefano Dalla Gasperina <[email protected]>
|
@rjohn-v Why does the |
|
I have no idea! It is supposed to be triggered on creation of a version tag, right? Also if doing a merge to any branch apart from main or develop, you can just do the merge locally on your machine and push to the branch |
|
Will do a merge locally. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.