Summary

Migrations to major versions of typescript become increasingly critical and more difficult the more major versions behind we are. As such, we should strive to stay at least one major version behind critical build tooling packages like typescript, as they directly affect maintainability of our product, and risk emergent problems when core features are sunsetted.

Motivation

Who is the affected end user?

Driver engineers, driver users.

How does this affect the end user?

They could be annoyed, as releases could lag pending waiting for core critical updates.

How likely is it that this problem or use case will occur?

Given a reasonable update cadence for our build tooling, it should rarely occur. The risk is in the delay.

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance. New features/bug fixes may lag in their release.

Is this issue urgent?

Light-urgency.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

This ticket should not cause any functional changes (though we cannot predict this, as a new feature could in-theory change our build output). Tests will likely need updates.

Cast of Characters

Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders:

Channels & Docs

Slack Channel

[Scope Document|some.url]

[Technical Design Document|some.url]