chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

hephaestus@0.77.0

Minor Changes

• Issue practice reviews now react to a title, description, label, assignment, milestone or reopen change on GitHub and GitLab, and to a native issue type change on GitHub — where before only a new label did. Closing an issue again after reopening it is now reviewed again too, instead of only the first close being. Practices already bound to the labelled occasion move to the wider one automatically on upgrade, keeping their customisations. Expect issue reviews to run more often: each round of triage that changes what a practice can read occasions its own review, there is no delay that batches a burst of edits into one, and the first backfill campaign after the upgrade reviews each already-closed issue once more. Locking an issue, pinning it, or editing a due date, weight or time estimate occasions nothing, and a replayed event or a return to an issue state already reviewed no longer starts another review.

Patch Changes

• Serving an instance on more than one hostname is now entirely the reverse proxy's job: the extra
  names, their shared certificate, and the redirect that sends a browser back to APP_HOSTNAME are all
  configured in one place. An instance that names a single hostname routes and serves exactly as
  before, and one fronted by a proxy that does not read this stack's routing configuration answers on
  whatever names that proxy sends it — configure the extra names and their redirect there instead.
• Restores the timeouts the bundled edge applies to the application server, so a backend that accepts a connection but never answers releases the browser with an error page instead of leaving requests and mentor chat streams hanging indefinitely. A host that keeps itself on its channel now starts the stacks in the order the migration requires, converges again when you promote the release it already runs, and no longer refuses to retry after a partly-applied deploy. Rolling back to a release published before GitHub offered immutable tags works again.
• The TUM-operated instance is now addressed as hephaestus.build. The imprint, the privacy
  statement, the in-app footer links, security.txt and the documentation all name it, and the older
  hephaestus.aet.cit.tum.de address continues to reach the same instance. Source links follow the
  repository to the hephaestus-build organisation; images and signatures for releases cut before the
  move keep their original namespace and signing identity, so verifying an older release is unchanged.
• An instance now sends Strict-Transport-Security whatever proxy sits in front of it. The header was
  attached to the reverse proxy shipped with Hephaestus, so a deployment fronted by a different proxy —
  a PaaS, or an existing ingress — served without it, and the omission was easy to miss because every
  other security header comes from the responses themselves. Nothing changes for a deployment that uses
  the bundled proxy.
• Pending practice reviews no longer run after reconciliation marks their issue, pull request, or merge request as deleted upstream. They resume automatically if a later sync finds the work again.