Projects platform versioning (BETA)
HubSpot developer projects include a
platformVersion field that enables you to control which version of the projects platform you're developing on. This enables you to access updated functionalities, rollback to previous versions, and generally coordinate changes as needed.
Below, learn how to set the
platformVersion in a project, along with the available versions and their updates.
To set which version of the developer platform your projects are running on, use the
platformVersion field in your project's
After changing the version number, you'll need to upload the project to the HubSpot account to enable access to the version updates.
The developer platform was initially released as version
2023.1. Below, learn more about other available versions.
- Latest version (November 21, 2023):
- Initial release:
Available as of November 21, 2023.
Changes primarily impact app functions, including:
Learn more about working with these changes below.
Initial release of the developer platform.
2023.2 of the developer platform includes the changes below.
The following changes have been made for serverless function configuration (
- Previously, serverless functions in projects supported two types of functions: app and API endpoint. App functions have been updated to support public URLs for making API requests, so you no longer need to build these as separate types.
- With this update, the
versionfields have also been removed.
- This version uses Node18, and lower versions cannot be specified.
Previous serverless function configuration
Updated serverless function configuration
Projects now support asynchronous functions. Callbacks are no longer supported in this version.
To update your serverless functions to use async:
asyncto the function definition.
- Remove the callback (sometimes referred to as
sendResponse), and use return statements to return response.
catchinstead of promise chaining.
- Return the desired response or throw an error.
Whereas previously you would refer to private app access tokens with
context.secrets.PRIVATE_APP_ACCESS_TOKEN, you'll now use
process.env rather than
context.secrets. For example:
Thank you for your feedback, it means a lot to us.