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.

Sign up for GitHub

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

Jump to bottom

Upgrading from Mjolnir or any version of Draupnir below v1.87.0 to Draupnir v2.0.* can cause some rooms to become unprotected. #706

Closed

Gnuxie opened this issue Jan 25, 2025 · 1 comment

Member

Gnuxie commented Jan 25, 2025 •

edited

Loading

This is now fixed, UPGRADE to V2.1.0

If you have config.protectAllJoinedRooms enabled, Draupnir does not seem to currently abide by the setting.

What to do if you upgrade regardless:

Compare the rooms that the bot is present within (by signing into the account) with the output of !draupnir rooms
If you have not protected or unprotected any rooms with Draupnir, it may be possible to downgrade from v2.0.0 to restore protection in these rooms. However, we have not verified this and we cannot advise it.

We are currently investigating the issue and will release a fix soon, rooms will be protected again once the config option is fixed.

We will provide a way to obtain a list of unprotected rooms with the fix. Sorry for any inconvenience caused and thank you for your patience

The text was updated successfully, but these errors were encountered:

Gnuxie pinned this issue

Member Author

Gnuxie commented Feb 2, 2025

Fixed in v2.1.0

Gnuxie closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment