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
{{ message }}
Repository navigation
Packages are not in sync with upstream tutor releases #73
tutor v22 was released last week.
Can we think of a process or solution to keep the packages up to date with the tutor releases?
Does it make sense to drop the "<v22.0.0" and only keep the ">vx.x.x"?
This is a per-plugin decision, but broadly speaking, I think it's safer for a plugin to declare an upper version limit. It's like saying, "we have only tested up to this version; no guarantees above that!". Then once the plugin is tested against a newer Tutor - maybe by a user such as yourself - we can bump it.
@CodeWithEmad it sounds like if you are testing with newer versions for specific plugins, you could just PR updated version bands. I'm gonna close this for now but feel free to open PRs for plugins that you have tested with newer versions of tutor and whose version bands can be updated.
Activity
arbrandes commentedon Aug 11, 2026
This is a per-plugin decision, but broadly speaking, I think it's safer for a plugin to declare an upper version limit. It's like saying, "we have only tested up to this version; no guarantees above that!". Then once the plugin is tested against a newer Tutor - maybe by a user such as yourself - we can bump it.
feanil commentedon Aug 14, 2026
@CodeWithEmad it sounds like if you are testing with newer versions for specific plugins, you could just PR updated version bands. I'm gonna close this for now but feel free to open PRs for plugins that you have tested with newer versions of tutor and whose version bands can be updated.