Skip to content

Use SemVer to check communication compatibility between C# and Python #3760

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Apr 9, 2020

Conversation

surfnerd
Copy link
Contributor

@surfnerd surfnerd commented Apr 8, 2020

Proposed change(s)

Use SemVer to check communication compatibility between C# and Python.

Useful links (Github issues, JIRA tickets, ML-Agents forum threads etc.)

MLA-822

Types of change(s)

  • Bug fix
  • New feature
  • Code refactor
  • Breaking change
  • Documentation update
  • Other (please describe)

Checklist

  • Added tests that prove my fix is effective or that my feature works
  • Updated the changelog (if applicable)
    - [ ] Updated the documentation (if applicable)
    - [ ] Updated the migration guide (if applicable)

Other comments

@surfnerd surfnerd requested a review from chriselion April 8, 2020 22:59
@surfnerd surfnerd self-assigned this Apr 8, 2020
…ests.cs


to make it slightly interesting

Co-Authored-By: Chris Elion <chris.elion@unity3d.com>
@surfnerd surfnerd changed the title Bump communication API to 1.0.0 in C# and Python. Use SemVer to check compatibility. Use SemVer to check communication compatibility between C# and Python Apr 9, 2020
…ibility outside of the initialization check.
@surfnerd surfnerd merged commit fe6a63f into master Apr 9, 2020
@delete-merged-branch delete-merged-branch bot deleted the master-semver-communication branch April 9, 2020 23:36
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants