v2024.9

Correct counting of indirect-failed packages, matching what pbulk does. See #70 and #72 for details. This means you won't see "indirect-failed" packages under failed dependencies any more. At least for new builds! Old ones will still use the old method.

Other changes:

• Build requires Go 1.22 now.
• Lots of cleanups, removing obsolete code and unused dependencies.

v2024.8

• New feature: show status of "sentinel packages" (i.e. meta-pkgs/bulk-test-*) prominently on the build results page, along with links to their failed dependencies (#71).
• Invert the order of tables on the package results page: show failed dependencies above other packages broken by this one, since it's arguably more important.
• Fix one bug that would have caused tables to remain in "Loading" state forever when there are no results to show.
• Add an internal handler allowing to delete details of a bulk build.
• refactorings and internal cleanups

v2024.7

• Piecharts are now generated with the bundled ChartJS instead of Google Charts
• Store and show errors when fetching details, providing a reason why there are no details for a certain build (#5)
• update README
• code cleanups

v2024.4.1

• Fix "packages broken by this package" display. It used to show matching packages from all builds, instead of just the current build.
• Fix for #51: link from package result to the build it was part of
• Fix for #52: link from bulk build page to the original machine-readable report URL
• Fix for #53: name the branch on package result page

Thanks to @riastradh for keeping the suggestions coming!

v2024.4

Major bugfix: also count indirect-failed dependencies in the list of "failed dependencies" of a package. This bug has been present in all BulkTracker versions ever. Note: this bugfix will only apply to reports sent after the BulkTracker version is upgraded on the server.

Others:

• Fix parsing of failed_deps in the display of package build results -- this means failed dependencies are actually displayed correctly (by @riastradh)
• Bump several dependency versions with security issues
• Use scheme-relative links to NetBSD.org, pkgsrc.org, pkgsrc.se (by @riastradh)
• Add an index for build_id and result_id for performance, also suggested by @riastradh
• Remove some debug log prints

v2024.3.1

Bugfix: honor base_path in package tables: Clicking a link in some package tables resulted in a 404 in the https://releng.netbsd.org/bulktracker/ instance (where base_path=/bulktracker/).

v2024.3: feat: show failed dependencies in package results.

• Restore "This package breaks n others" table
• Restore "This package has n failed dependencies" table

v2023.12

• Fix for #48: correct display of the "All Builds" page
• Bump Go crypto library as a security fix

2023.11.1

Closed a number of bugs mentioned on the NetBSD mailing list and here:

• #42 Category page has broken links to packages (also reported by kre@ via email)
• #43 Package page has broken link to build results
• #44 Home page has unnormalized links to categories
• #45 Build result page has broken links to categories
• #47 Package page has broken link to package location

Thanks @rillig for these reports!

2023.11

Fix for #41: Now you can add the new -base_path option to attach the UI under a subdirectory.