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
A common source of bugs with sunbeam extensions is having extensions that aren't up to date with recent GitHub changes. This is the price we pay for trying to walk the line between having a proper version control/matching system for sunbeam with its extensions and just making everything fully backwards/forwards compatible.
Something that might make this problem more palatable is a system to check that all extensions are up to date with GitHub main/master branches (maybe at start of run, maybe a separate command, maybe only on error?).
The text was updated successfully, but these errors were encountered:
What's the feature?
A common source of bugs with sunbeam extensions is having extensions that aren't up to date with recent GitHub changes. This is the price we pay for trying to walk the line between having a proper version control/matching system for sunbeam with its extensions and just making everything fully backwards/forwards compatible.
Something that might make this problem more palatable is a system to check that all extensions are up to date with GitHub main/master branches (maybe at start of run, maybe a separate command, maybe only on error?).
The text was updated successfully, but these errors were encountered: