Publish sha512 checksums for Aspire Dashboard
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
Related:
- https://github.com/dotnet/dotnet-docker/issues/6568
- https://github.com/dotnet/dotnet-docker/issues/5154
Publishing SHA512 checksums for the aspire dashboard zip/archive files will make updating the dotnet-docker repo significantly simpler. It looks like we can use the same pattern as for the Aspire CLI.
Here's some places in the code that looked relevant for this:
https://github.com/dotnet/aspire/blob/41f4f6fbdbf4a230e7efb978a3551e671bebd448/eng/Publishing.props#L65-L75
https://github.com/dotnet/aspire/blob/41f4f6fbdbf4a230e7efb978a3551e671bebd448/eng/dashboardpack/Common.projitems#L47-L51
/cc @joperezr
Contributor guide
Research direction
Start by comparing the Aspire CLI checksum pattern in eng/Publishing.props with the dashboard entries in eng/dashboardpack/Common.projitems. Trace how the dashboard zip/archive files are published, then verify that SHA512 checksums are produced for those artifacts so dotnet-docker can consume them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100