Skip to content
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

use hotfix mps-extensions version #2707

Draft
wants to merge 1 commit into
base: maintenance/mps20241
Choose a base branch
from

Conversation

wsafonov
Copy link
Member

[A short explanation of your PR]

Checklist for creating a good PR (can be deleted)

  • I've described my change in the CHANGELOG.md if it is visible to users of the platform (mandatory).
  • I've selected the correct base branch.
  • I have checked my code (edge cases, no errors) and corrected any misspellings.
  • I have added comments to my code in areas where the code is hard to understand.
  • I've created a new language/solution.
    • I've added the language/solution to the build script (tutorial in readme)
    • I've added a sandbox that showcases the language.
    • There is some kind of documentation available in the repository or somewhere else [e.g. MPS Platform Docs].
  • I've introduced a breaking change.
    • I've made it clear that a change is breaking e.g. [breaking] prefix in the title
    • I have written new tests/changed old tests.
    • I have created migrations when necessary (e.g., deprecation of concepts, properties, enumeration values).
    • I haven't removed concepts, properties, references, or children without deprecating them first.
    • I have moved nodes or models by using the refactoring move action.

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