Skip to content

Fixing Zammad 6.5 API-Changes #25

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 4 commits into from
May 8, 2025
Merged

Conversation

RincewindsHat
Copy link
Member

Trying to fix #23

@RincewindsHat RincewindsHat requested a review from martialblog May 5, 2025 08:09
@RincewindsHat RincewindsHat force-pushed the fix/zammad-6.5-changes branch from 46729ce to 130e19f Compare May 5, 2025 08:14
Copy link
Member

@martialblog martialblog left a comment

Choose a reason for hiding this comment

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

Besides, some left over println - looks good

@citfs
Copy link
Collaborator

citfs commented May 6, 2025

works on my machine <(^_^)>

@martialblog martialblog added this to the v0.2.0 milestone May 7, 2025
@martialblog
Copy link
Member

@RincewindsHat You can merge this and tag v0.2.0 if you want. Should we add a note about the API change somewhere in the README?

@RincewindsHat
Copy link
Member Author

@martialblog I added a note to the README

@RincewindsHat RincewindsHat marked this pull request as ready for review May 8, 2025 14:41
@RincewindsHat RincewindsHat merged commit e622e6b into main May 8, 2025
2 checks passed
@martialblog martialblog deleted the fix/zammad-6.5-changes branch May 8, 2025 14:50
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.

[Bug]: Notifications not working after Upgrading to Version 0.1.1-1.bookworm
3 participants