Skip to content

chore: keeping Yamato tests at 2022.3.14 until editor is upgraded #882

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 1 commit into from
Mar 1, 2024

Conversation

fernando-cortez
Copy link
Collaborator

@fernando-cortez fernando-cortez commented Mar 1, 2024

Description

PR to keep project metafile version number locked at our current editor version, since Yamato is reporting failures at the latest 2022.3.x release.

This is a temporary addition, and will be reverted once KTLO is started, which will include editor bump.

Issue Number(s)

None, but MTT-8160- has been created to track this workaround for testing.

Contribution checklist

N/A - just looking for tests to succeed so that subsequent PRs targeting this version can be merged.

  • [ N/A ] Tests have been added for boss room and/or utilities pack
  • [ N/A ] Release notes have been added to the project changelog file and/or package changelog file
  • [ N/A ] Pull request has a meaningful description of its purpose
  • [ N/A ] All commits are accompanied by meaningful commit messages
  • [ N/A ] JIRA ticket ID is in the PR title or at least one commit message
  • [ N/A ] Include the ticket ID number within the body message of the PR to create a hyperlink
  • [ N/A ] An Index entry has been added in readme.md if applicable

Copy link
Contributor

@Elfi0Kuhndorf Elfi0Kuhndorf left a comment

Choose a reason for hiding this comment

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

Thank you!

@fernando-cortez fernando-cortez merged commit 43a00ed into develop Mar 1, 2024
@fernando-cortez fernando-cortez deleted the chore/keeping-yamato-tests-at-2022.3.14 branch March 1, 2024 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0-URGENT Blocker for a release and needs to be merged ASAP 0-workaround 1-Needs Review PR needs attention from the assignee and reviewers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants