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

[20241217] merge compatible into develop #16436

Merged
merged 11 commits into from
Dec 18, 2024
Merged

Conversation

dannywillems
Copy link
Member

Explain your changes:

  • git checkout develop && git fetch && git reset --hard origin/develop && git checkout compatible && git reset --hard origin/compatible && git checkout develop && git checkout -b dw/merge-compatible-20241217 && git merge compatible

Explain how you tested your changes:

  • N/A

Checklist:

  • Dependency versions are unchanged
    • Notify Velocity team if dependencies must change in CI
  • Modified the current draft of release notes with details on what is completed or incomplete within this project
  • Document code purpose, how to use it
    • Mention expected invariants, implicit constraints
  • Tests were added for the new behavior
    • Document test purpose, significance of failures
    • Test names should reflect their purpose
  • All tests pass (CI will check this if you didn't)
  • Serialized types are in stable-versioned modules
  • Does this close issues? List them
  • Closes #0000

@dannywillems dannywillems requested review from a team as code owners December 17, 2024 11:31
@dannywillems
Copy link
Member Author

!ci-build-me

@volhovm volhovm merged commit c74d243 into develop Dec 18, 2024
43 checks passed
@volhovm volhovm deleted the dw/merge-compatible-20241217 branch December 18, 2024 10:55
Copy link
Member

@querolita querolita left a comment

Choose a reason for hiding this comment

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

Looks good to me. But I have a question. The new commit checked out for snarky does not seem to be the current master but a commit from 11thDec. I can see you have made commits into the master branch ever since. Is that expected? Or should those other changes be also included and thus check out a6d3ccbf4e4ffdea595fc2c9bb17fbea8033fc9c instead?

@dannywillems
Copy link
Member Author

Looks good to me. But I have a question. The new commit checked out for snarky does not seem to be the current master but a commit from 11thDec. I can see you have made commits into the master branch ever since. Is that expected? Or should those other changes be also included and thus check out a6d3ccbf4e4ffdea595fc2c9bb17fbea8033fc9c instead?

It will be updated with @mrmr1993 PR here: #16433

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.

7 participants