Skip to lesson
Exit
Turn a dependency audit into a canvas1 / 1

2 min lesson

Source-backed table, data refresh, publish boundary

Practice Canvases on one real case. Check the result before moving on.

Check your understanding

Complete the practice "Canvas, turn a dependency audit into an upgrade decision".

Outcome: The team-visible snapshot opens with its source commit and run time. The handoff still points reviewers to the lockfile and pull request for the live change.

Canvas, turn a dependency audit into an upgrade decision
Source-backed table, data refresh, publish boundary
SayThe engineering lead must choose which dependencies to upgrade this sprint. Ask for a canvas that keeps the decision and its source together.
TypeRun this repository's dependency audit commands. Open a canvas with package, current version, target version, advisory, severity and recommendation. Sort by severity. Show the source commands, commit and run time.
DoOpen the canvas card at the end of Agent's response. Check the summary count, then compare one high-severity row with the terminal output and lockfile.
SeeThe canvas answers which packages need work first, and the checked row matches the named source data.
SayThe target version and advisory count look stale. Rerun the underlying commands and show the work. Do not hand-edit the numbers.
SeeAgent refreshes the data. The canvas now shows the new run time, and its counts match the command output.
DoAsk Agent to add one short caveat for packages that need manual compatibility review. Keep the table fields and sort order unchanged.
SeeThe caveat sits beside the affected rows instead of disappearing in a closing paragraph.
DoBefore Publish, confirm the plan, team, admin setting and privacy mode permit sharing. Open the published link as the intended teammate.
SeeThe team-visible snapshot opens with its source commit and run time. The handoff still points reviewers to the lockfile and pull request for the live change.
Learn more

Optional practice

Test yourself on Source-backed table, data refresh, publish boundary

QWhich result proves the dependency canvas is ready to share?

Finish the check to continue.