This page lists the major changes in each release of Google Apps Script in 2015. It is intended to help developers identify changes in behavior. For more recent changes, see the current year's release notes.
December 10, 2015
- In the HTML service, EMULATED sandbox mode was sunset. Any scripts that explicitly request EMULATED mode now default to IFRAME mode.
November 12, 2015
- In the HTML service, all new scripts default to IFRAME sandbox mode unless NATIVE mode is explicitly specified.
August 10, 2015
- Deprecated the method
ScriptAppglobal object. This method is no longer useful because Apps Script's authorization model has changed since the time the method was introduced.
August 4, 2015
- Added the following methods to the Spreadsheet service to let scripts control "warning-based" protection for spreadsheet ranges (which means that every user can edit data in the area, except editing prompts the user to confirm the edit):
June 30, 2015
- Added two variations of the method
Utilitiesglobal object to let scripts sign a string using the RSA SHA-256 algorithm.
May 27, 2015
- Added the method
HtmlServiceglobal object to let scripts get the user-agent string for the current browser.
May 20, 2015
- Added the following enum and methods to the Script service to allow scripts to identify their installation source and project keys:
- Added several new web-safe base-64 encoding and decoding methods:
- Deprecated the following OAuth class and methods in favor of OAuth libraries:
April 23, 2015
- Add-ons are now out of developer preview. This means anyone can now publish an add-on. New add-ons will still be reviewed prior to publishing, but the publishing process has been streamlined.
- Add-ons can now be developed and published from standalone scripts (as opposed to scripts bound to a Sheet, Doc, or Form). The add-on must still operate on a Sheet, Doc, or Form, but the script does not need to be bound to a single master file. Developing from a standalone script is preferred in that it makes collaboration and testing easier.
- Add-on scripts in development can be tested to ensure they behave as intended.
- The DocsList service, which was deprecated in 2014, has been sunset and no longer functions. Users relying on DocsList should switch to DriveApp.
March 19, 2015
- Added the ability to publish add-ons for domain-wide installation. This lets an admin of a Google Apps domain install and authorize a Docs, Sheets, or Forms add-on for all users in the domain if the add-on is published to the Google Apps Marketplace. If the developer has already published a Google Apps Marketplace app that is closely related to their add-on, they can also choose to bundle the add-on with the Marketplace app so that admins install both the app and the add-on together.
- Added the ability to change the Google Developers Console project that a script uses for authorization. This feature is most commonly used to bundle an add-on with a Google Apps Marketplace app, as above.
March 4, 2015
- Deprecated the URL Fetch service's class
OAuthConfig, which provided the ability to connect to OAuth 1.0 APIs. This has been replaced by the open source library OAuth1 for Apps Script. See the migration guide for more information.
February 10, 2015
- Added the following class, enum, and methods to the Spreadsheet service, to give precise control over protected sheets and ranges:
- Deprecated the following class and methods, which have been replaced by the
Protectionclass above. Although this class and these methods are deprecated, they will remain available for compatibility with the older version of Sheets.
- Replaced the method
SpreadsheetApp.open(file), which takes a
Fileobject from the deprecated DocsList service as a parameter, with a version that takes a
Fileobject from the Drive service instead. The new method has the same name.
- Changed several
Spreadsheetmethods that previously returned
voidso that they now return a
Spreadsheetobject that can be used to chain method calls.
- Changed the Document service methods
Text.setFontFamily(fontFamilyName)to use string names for font families instead of the
FontFamilyenum, and consequently deprecated
- The following fix was applied: