[GH-ISSUE #642] Catch bad releases earlier with tests against published artifacts #261

Open
opened 2026-03-07 23:05:39 +03:00 by kerem · 0 comments
Owner

Originally created by @bluejekyll on GitHub (Dec 21, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/642

Is your feature request related to a problem? Please describe.

Releases sometimes are minor, and don't always involve publishing all crates, there is a chance in this case of breaking especially optional artifacts. See: #640

Describe the solution you'd like

Create a new test in Travis(?) that will build crates after they are published

Originally created by @bluejekyll on GitHub (Dec 21, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/642 **Is your feature request related to a problem? Please describe.** Releases sometimes are minor, and don't always involve publishing all crates, there is a chance in this case of breaking especially optional artifacts. See: #640 **Describe the solution you'd like** Create a new test in Travis(?) that will build crates after they are published
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#261
No description provided.