Skip to content

Conversation

@NikolaBabadzhanov
Copy link

The two pull requests are from our fork of the repo. When my PR was approved, it has never been merged (it seems so). Thus, I am raising them again.

@jthDEV
Copy link
Collaborator

jthDEV commented Jan 5, 2026

Hi Nikola, thank you for your commit and the reminder. Unfortunately I am not able to identify your changes. Not sure , whether this has to do with the way your are structuring your pull request. But looking into the capability map, I still see v1.6.4.

@OliverFendt
Copy link
Contributor

@NikolaBabadzhanov thank you for your efforts. On slide 1 there is still Version 1.6.4 mentioned, it should be version 1.6.5 and on slide 45 the version 1.6.5. is missing too.

@NikolaBabadzhanov
Copy link
Author

Perhaps, as at the time the slides where created it was still 1.6.4, thus, historically it was right at the time. Let me know whether I should close it and raise it a new. The version on our fork is indeed 1.6.4. Alternatively, I can update the version on our fork and update the PR. Let me know what you think.

@NikolaBabadzhanov
Copy link
Author

And my bad, it seems the changes from the original PR I raised where merged with commit 4d44fc7. Thus, this one is irrelevant. I am closing the PR. I will fix the fork later. Sorry for wasting your time :)

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.

3 participants