You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compose is main branch has not been updated following the release of 2.0.6.
Fresh install shows an update available.
Expected Behavior
Not seeing an update available on latest commit
Steps To Reproduce
Fresh install / open reNgine
Environment
Latest, right now, rest is irrelevant
Anything else?
To avoid this from happening, github actions should be configured to create a tag / release when a file (specific or in .py, doesn't matter) is updated with a new version number instead of manually creating them and risking forgetting.
The text was updated successfully, but these errors were encountered:
👋 Hi @Talanor,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.
Is there an existing issue for this?
Current Behavior
Compose is main branch has not been updated following the release of 2.0.6.
Fresh install shows an update available.
Expected Behavior
Not seeing an update available on latest commit
Steps To Reproduce
Fresh install / open reNgine
Environment
Anything else?
To avoid this from happening, github actions should be configured to create a tag / release when a file (specific or in .py, doesn't matter) is updated with a new version number instead of manually creating them and risking forgetting.
The text was updated successfully, but these errors were encountered: