You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2023. It is now read-only.
In August, we're going to release new version of Unified CI with Go 1.21 support. With that release, we'd like to transition to Unified CI 2.0 which should encompass all the learning that we gathered by running Unified CI in its' current form for years. This includes but is not limited to:
versioning Unified CI
embracing reusable workflows
centralising auomerge functionality
allowing configurability through dot files
simplifying enrollment with invite to deploy strategy
All of the above will make Unified CI more robust, easier to manage and it will increase it chances to last for another couple of years. Moreover, it will open up doors for even more automation across hundreds of repositories, like using dependabot (instead of web3-bot that has to be maintained by IPDX) for Unified CI updates, or maintaining multiple variants of releaser workflows (e.g. release-please vs version.json vs PR).
The text was updated successfully, but these errors were encountered:
eta: 2023-08
Tasks
description: https://github.com/pl-strflt/ipdx/blob/master/ROADMAP.md#release-unified-ci-20
In August, we're going to release new version of Unified CI with Go 1.21 support. With that release, we'd like to transition to Unified CI 2.0 which should encompass all the learning that we gathered by running Unified CI in its' current form for years. This includes but is not limited to:
All of the above will make Unified CI more robust, easier to manage and it will increase it chances to last for another couple of years. Moreover, it will open up doors for even more automation across hundreds of repositories, like using dependabot (instead of web3-bot that has to be maintained by IPDX) for Unified CI updates, or maintaining multiple variants of releaser workflows (e.g. release-please vs version.json vs PR).
The text was updated successfully, but these errors were encountered: