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
@@ -402,60 +401,57 @@ async function prepareGitEnvironment(): Promise<void> {
402
401
403
402
// updates the release.config.json file for the sla field, which contains a release history of start and end date support
404
403
// inspired by node: https://github.com/nodejs/Release/blob/main/schedule.json, following https://github.com/nodejs/release#release-schedule, leveraging https://github.com/nodejs/lts-schedule
Copy file name to clipboardExpand all lines: website/docs/contributing/CI/overview.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,6 @@
3
3
The CI runs on Github Actions and tries to be as efficient as possible by only running the required steps based on the changes.
4
4
To achieve this, it's using a combination of caches and artifacts, with [matrix jobs](https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs) to run only certain languages.
5
5
6
-

7
-
8
6
## Note on JavaScript
9
7
10
8
JavaScript CI is highly specialized and contains many differences with the other clients, so it has it's own dedicated steps.
Copy file name to clipboardExpand all lines: website/docs/contributing/release-process.md
-18Lines changed: 0 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,21 +40,3 @@ You need approval from a member of the [`@algolia/api-clients-automation`](https
40
40
After a full CI run, a release commit will be sent to every repository and spread changes to their `next` branch.
41
41
42
42
Each language repository should have their own release process, and should run only when the latest commit starts with `chore: release`. By doing so, we have a way to just update the repository, for example READMEs, without having to release.
43
-
44
-
## SLA graph
45
-
46
-
In order to generate the SLA graphs ([available here](/docs/clients/service-level-agreement)), we leverage the open-source Node.js tools:
47
-
-[JSON input format file](https://github.com/nodejs/Release/blob/main/schedule.json)
48
-
-[script](https://github.com/nodejs/lts-schedule)
49
-
50
-
The source of truth data lives in [the release config file](https://github.com/algolia/api-clients-automation/blob/main/config/release.config.json), under the `lts` field.
51
-
52
-
### Patch `lts` package
53
-
54
-
The [`lts`](https://github.com/nodejs/lts-schedule) package has been patched (with `yarn patch lts`, see diff in `.yarn/patches`), if you edit the patch, make sure to run `yarn patch-commit -s /path/to/your/patch/folder` in order to update the lock.
0 commit comments