Brackets checks for updates by downloading a copy of this JSON info from a fixed S3 URL. Updating this repo does not automatically push the changes "live" to S3. This repo is used to discuss changes and prepare translations before the updates files go live.
To push new update files
Note: Beginning with Release 39 all update JSON files are available from https://s3.amazonaws.com/files.brackets.io/updates/stable
There is a nodejs script that will take care of uploading the update notifications into the S3 bucket. The script will preserve all attributes on existing files in the S3 bucket. In order to deploy the update notifications to S3, some required libs have to be installed upfront.
- cd into
scriptsdirectory and replace the placeholder with your AWS AccessKey and SecretKey (ask Ryan, Kevin or Ingo for these information)
Prepare the update notification
NOTE: Running this script will replace the current files in the S3 bucket. There is no backup of the existing files and the update notification are immediately visible to everybody using Brackets.
- Make sure the JSON parses cleanly (you can use http://jsonlint.com, but the errors might not be as good as calling
- Check the files into this repo's master.
- Open a terminal and cd into
./create-gzipped-jsons.sh. This will create a new folder
GZIPPED_JSONSwith the gzipped version of the update notification.
To check update appearance in Brackets
UpdateNotification._getVersionInfoURL()to always return...
- A local URL like: file://C:/code/brackets-updates/updates/stable/en.json
- A GitHub raw URL like: https://raw.githubusercontent.com/adobe/brackets-updates/master/updates/stable/en.json
(this can point at version on a PR's branch, too)
- Reload, then Help > Check for Updates