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
After the incident that occurred last Sunday, I've enabled support for pre-releases for Vibrancy releases that haven't been thoroughly tested. This means that people who want to try the latest changes and help the project in a more passive way can do so by switching to the pre-release version using the drop-down menu in the Extension's tab.
You can expect that new releases will now occur less often, but will also be more reliable, and errors will be caught earlier on if enough people sign up for pre-releases and help report any new issues.
Main branch rename
Additionally, the master branch was renamed to main, and a development branch has been created to facilitate pre-releases. All PRs now must target the development branch. To update your local copies of Vibrancy for development purposes, you can run these commands:
git branch -m main main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
After the incident that occurred last Sunday, I've enabled support for pre-releases for Vibrancy releases that haven't been thoroughly tested. This means that people who want to try the latest changes and help the project in a more passive way can do so by switching to the pre-release version using the drop-down menu in the Extension's tab.
You can expect that new releases will now occur less often, but will also be more reliable, and errors will be caught earlier on if enough people sign up for pre-releases and help report any new issues.
Main branch rename
Additionally, the
master
branch was renamed tomain
, and adevelopment
branch has been created to facilitate pre-releases. All PRs now must target thedevelopment
branch. To update your local copies of Vibrancy for development purposes, you can run these commands:Beta Was this translation helpful? Give feedback.
All reactions