[NPMCLI-154] Add upgrade notice about incompatible prototype files Created: 13/Dec/17 Updated: 23/Feb/18 Resolved: 23/Feb/18 |
|
| Status: | Closed |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | AntonĂn Juran |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | CLI v3 | ||||||||
| Sprint: | Kromeriz 134, Kromeriz 135 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
Use the standard npm approach to display a message on upgrade to v3 that any existing customized prototypes are now obsolete and must be migrated. |
| Comments |
| Comment by Jaroslav Simak [ 20/Feb/18 ] |
|
ajuran Can you please implement postinstall hook? So at least users that will update via npm install will get notified? The npm update doesn't offer possibility of hooks. Thanks. |