[FOLIO-3768] do not rebuild yarn.lock from scratch for hotfixes on release branches Created: 27/Apr/23 Updated: 26/Jun/23 Resolved: 26/Jun/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Zak Burke | Assignee: | oleksandr_haimanov |
| Resolution: | Done | Votes: | 0 |
| Labels: | reviewed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | Kitfox: sprint 168 | ||||||||||||
| Story Points: | 2 | ||||||||||||
| Development Team: | Kitfox | ||||||||||||
| RCA Group: | TBD | ||||||||||||
| Description |
|
Summary: Instead of rebuilding yarn.lock files from scratch for hotfixes on release branches, we should retain yarn.lock from the previous release and only include new versions of third-party libraries that are a direct result of updating versions in package.json. If we had leveraged the existing R3-2022-GA yarn.lock file for the R3-2022-hotfix-1 build instead of rebuilding it from scratch, i.e. only updated packages when they were required by version changes made in package.json, we would have limited the scope to 7 version changes, all directly related to FOLIO. Instead, we pulled in 258 version changes. |
| Comments |
| Comment by oleksandr_haimanov [ 26/Jun/23 ] |
|
Closing |