Jump to
Product Updates
v24.45 v24.40 v24.36 v24.27 v24.23 v24.17 v24.13 v24.09 v24.05 v24.01 v23.48 v23.44 v23.39 v23.31 v23.27 v23.27.1 v23.24 v23.19 v23.19.1 v23.14 v23.14.1 v23.12 v23.10 v23.08 v23.06 v23.04 v23.02 v22.52 v22.50 v22.48 v22.46 v22.44 v22.42 v22.40 v22.38 v22.36 v22.34 v22.32 v22.30 v22.28 v22.26 v22.24 v22.22 v22.20 v22.18.1 v22.16 v22.14 v22.10 v22.08 v22.06 v22.04 v22.02 v21.51 v21.49 v21.47 v21.45 v21.43 v21.41 v21.39 v21.37 v21.35 v21.33 v21.31 v21.27 v21.23 v21.19 v21.14 v21.10 v21.06 v21.02 v20.51 v20.47 v20.43 v20.39 v20.35 v20.31 v20.27 v20.23 v20.19 v20.15 v20.11 v20.07 v20.03
Updated on

Product Update - v22.12

Details of the product update v22.12 from 28th of March 2022.

Features

Automated component deployments

In platform version 22.12 we are releasing the new automated component deployment feature. We introduced the underlying concept with the version 22.04 release at the end of January 2022. Here is the final workflow of the automated component deployments:

  1. A new version (tag) is created in the GitHub component repository and the release is published.
  2. The CircleCI build process uses appbuilder + apprunner images.
  3. A Docker image of the component is built with the tag version and submitted to Dockerhub.
  4. An additional latest version is created in Dockerhub each time the code is updated.
  5. The platform runs a Kubernetes platform job called components-pusher at certain intervals checking the component Dockerhub latest version.
  6. If the version in Dockerhub differs from the existing platform version it pulls a new Docker image and pushes it into the platform docker registry.
  7. A new version of component is released for the platform users and can be selected while designing flows.

Please Note - we determine and set the configuration of platform components-pusher in HELM3 deployment charts. These configurations provide more options for each component. Here we present the typical scenario.

The automated component deployment process works along with the old git-push workflow. You can push components via git receiver as well. The components-pusher will not interfere with your pushed version.

Improvements and Updates

Node.js Sailor version 2.6.27

We released a new version (2.6.27) of the Node.js Sailor library version. This version includes an npm audit to CI and updated dependencies.

UX Improvements: credentials page

To improve the user experience on the credentials page we added the component team and repository name to which this credential belongs. This helps in distinguishing between different deployments of components and in choosing the correct component for credential modification.

Credentials page Improvements

The above images show two different repositories of the same component. The new improvement shows the difference between these two components.

Fixed bugs

  • Addressed the issue when the “Server error” message would show while navigating through the UI upon the session expiration.
  • Fixed the bug causing the system to erroneously send “New sign-in to your account” emails. The expired sessions were not deleted from the system.
  • Addressed the issue with the “Mapping” configuration field showing up in UI for the trigger functions on components.

Components

With introduction of automated component pusher we change the standardise component build procedures preparing them for components-pusher service. The following component build configurations were changed:

GraphQL component 1.1.1

  • ADDED No Auth, Basic Auth and API Key Auth authentication methods
  • ADDED a new action Raw Request
  • ADDED a new action Configured Request

Shopify admin component 1.5.0

  • ADDED: a new action Update Inventory Level
  • FIXED the output metadata for Get New And Updated Objects Polling trigger

PayPal component 1.0.0

  • ADDED: a new action Make Raw Request

Vtex component 1.2.0

  • ADDED: a new action Lookup Set Of Objects By Unique Criteria