0.5.2 Starting with Themes

New

• Open Github pages for themes (as can be done with plugins)
• Switch to a different installed theme from command pallet

0.5.1 Small fix - no console.log()

0.5.0 Readme update

0.5.0 Enable/Disable plugins from CP

New

• Disable/enable plugins through command palette. Thanks to @menagerie198 - Issue

Improved

• Updates now report the previous version and new version number for plugin updates. Thanks to @SkepticMystic - Issue

0.4.4 Fix for plugin reload after restart

If a plugin was enabled and then updated, it was not being reloaded. This is now fixed

0.4.3

New

• Command Palette command to open a GitHub repository for a plugin

Fix

• Plugin now installs and loads the plugin without requiring the user to take additional steps
• if a plugin is updated by BRAT but not an enabled plugin, BRAT won't automatically enable it.

Changes

• New logic for how plugin is updated

if repositoryRoot/manifest-beta.json exists
use repositoryRoot/manifest-beta.json for release information, ignore repositoryRoot/manifest.json
copy repositoryRoot/manifest-beta.json to plugin folder, renaming it to manifest.json
else
use repositoryRoot/manifest.json for release information
copy Release/manifest.json to the plugin folder if it exists. If it doesn't exist, use the repositoryRoot/manifest.json

main.js and styles.css copied from the correspondencing release version depending upon the above logic

0.4.2

New

• Command Palette command to open a GitHub repository for a plugin

0.4.1 New processing workflow for manifest-beta.json

Fix

• Plugin now installs and loads the plugin without requiring the user to take additional steps

Changes

• New logic for how plugin is updated

new logic for plugins

if repositoryRoot/manifest-beta.json exists
    use repositoryRoot/manifest-beta.json for release information, ignore repositoryRoot/manifest.json
    copy repositoryRoot/manifest-beta.json to plugin folder, renaming it to manifest.json
else
    use repositoryRoot/manifest.json for release information
    copy Release/manifest.json to the plugin folder if it exists. If it doesn't exist, use the repositoryRoot/manifest.json

main.js and styles.css copied from the correspondencing release version depending upon the above logic

0.4 bug fixes

Added more error handling for improperly configured plugins and not installing them :-)

0.3

New: Add repo button in settings

0.2

New

• When adding new plugin paths, this plugin is a little smarter in converting them for use
• Added a Only check for updates to beta plugins, but don't Update
• Added ability to update just one beta plugin, along with the exsiting ability to check and update all plugins