In this release we migrated our internal git service to GitHub. All apps' internal git repositories are now hosted on GitHub. This has a number of advantages, namely:
- Simplifies our internal gitops.
- We are now in a position to give team members direct access to an app's internal git repository.
- Allows for deeper gitops integration between GitHub and the Meya Console.
Currently the recommended workflow is to host a separate git repo for your app with GitHub, and then use the Meya CLI to do a
meya push in a GitHub action when there is a commit to your
master branch. Now that an app's internal repo is already hosted on GitHub, we can add team members as external collaborators directly on the app's repo. Please contact [email protected] if you would like access to your app's internal git repo.
- We've fixed an internal db connection issue with the data retention service.
- We fixed an account permissions bug when deleting an app.
This release mainly contains platform fixes and performance improvements.
- We improved the Front integration's retry logic and now correctly observe the
Retry-Afterheaders when the integration receives
429rate limiting responses. This will provide improved reliability under heavy user traffic, where the integration will backoff and retry the requests later to improve message delivery.
- We improved our internal Redis connection handling to account for bad infrastructure nodes as reported in this incident. This will provide improved app infrastructure reliability under heavy app load.
In this release we upgraded the Python version in the base app container image to the latest version of Python: 3.10. Python 3.10 introduces a number exciting new language features that could be useful in your custom element code.
To update your apps, you can click the Rebuild button in app settings in the console. We recommend testing a
dev app first, in case your code has any compatibility issues. The main things to look for are older custom Python dependencies and old Python 2 compatible standard library imports.
For full details of the changes, including new features now available, you can refer to the official Python release notes:
If you have any questions or run into any issues updating your apps, please let us know!
All app pushes to
staging apps, as well as doing a build image for
dev apps, are now asynchronous. Previously all builds were limited to a maximum time of 2mins, however, asynchronous builds can now take up to a maximum time of 30mins. This allows you to do more work in your
install.sh script when installing custom Python dependencies that your app might require.
If you’re using the
startApp GraphQL mutations, you will now need to poll the app state to determine when the app is
running. The meya cli
v2.7.10 will automatically poll the app state on
meya push and
meya start commands. The meya console now also has an improved user experience when tracking the state of apps being built and deployed.
With asynchronous builds we also introduced a new app state changes and added some new push states:
buildingstate was removed.
startingstate was added. The app only goes into the
startingstate when the app is initially started. In this state the meya console creates the initial infrastructure for your app runtime.
cancelledstate was added. We now allow you to cancel a push that is in the
buildingstate was added. This indicates when the console is building your app's container image. This is when your app's
install.shscript is typically run.
deployingstate was added. This indicates that the push is updating your app's deployment, swapping the existing app runtime with your new app image.
For more details of app types, app states and push states check the App Types & States page.
- Improved app memory performance.
- Improved app infrastructure reliability.
Check Meya.ai updates for details on older releases and announcements.
Updated 6 days ago