Release Tracking #3341
Description
This is a scheduled issue for tracking the release between Monday 29th and Friday 2nd
| Last week | Value |
|---|---|
| Issue | Release Tracking |
| Conductor | siddharthkp |
| Release Pull Request | Link |
| Integration tests | Link |
Timeline
- Monday 29th
- US Holiday
- Tuesday 30th
- Dove into integration PR
- Seems like there are issues related to changes in
SelectPanelwhich seem related to Refactor FilteredActionList to address a11y violations and use new ActionList. #3247
- Wednesday 31st
- Label for checkbox changes
- Revert "Refactor FilteredActionList to address a11y violations and use new ActionList." #3349
- Thursday 1st
- Friday 2nd
- Draft PR with changes: https://gh.io/AAksvw0
- Still waiting on Revert "Refactor FilteredActionList to address a11y violations and use new ActionList." #3349 to be merged
Checklist
- Checks have passed on the integration Pull Request downstream
- Release tracking Pull Request has been merged
- Stable release available on npm
- Downstream repos have been updated to latest
Notes
- Upstream issues
SelectPanelchanges no longer work with deprecatedItemPropsdefinitions which are used- Changes to required inputs require upstream changes around the accessible name of a component
- ToggleSwitch changes can impact queries which rely on a single button
- Migrations from deprecated to latest have been causing some release problems or the past couple of months
- Something that may be helpful to include in our checklist for these migrations is a thorough testing of the current API before doing the migration
- Would it be possible to see the "fully expanded types" to make it more obvious when a regression occurs at the type level?
- Questions
- Are we okay recommending teams to include
*in their getByText queries? - Are changes to roles considered a breaking change?
- Often used in
getByRolequeries
- Often used in
- Are we okay recommending teams to include
Metadata
Metadata
Assignees
Labels
No labels