History subcommand

Description of the new feature / enhancement

Some other package managers keep track of history of operations. For example, see History Command in dnf manual. Having similar functionality available in Winget would be very useful. In particular, winget packages very often have upgrade path bugs, and writing an accurate bug report would require knowledge of how the package was installed, and when. winget history Troublesome.Package would help a lot there.

Proposed technical implementation details

I do not have very specific requirements for this. I think dnf's approach where every applied transaction is good. I think the following would be enough for the need I have:

• Transaction date
• Package IDs
• Version numbers from
• Version numbers to
• Operation type: install, upgrade or remove

(I am not sure if Winget does transactions, or just single package upgrades in sequence — if there are no transactions, then just logging individual operations in sequence would be enough.)

The issue names no files, tests, or entry points. Start by determining whether Winget records transactions or individual package operations and where that information could be retained; done means a history command can report dates, package IDs, previous and new versions, and install, upgrade, or remove operations.