Release v0.2.2

Part of the org-wide Actions throttling remediation. Mechanical, rule-based sweep:

• timeout-minutes on every job that had none (previously 6 h default): quick checks 15, builds 30, publish/release 60, integration/benchmarks 120.
• concurrency + cancel-in-progress only on pull-request-triggered verification workflows — never on publish/release/deploy, pull_request_target, workflow_run or reusable (workflow_call) workflows.

Every edited file re-parsed as YAML before commit. Files changed:

• .github/workflows/auto-approve-publish-deployments.yml
• .github/workflows/build.yml
• .github/workflows/cleanup-pr-artifacts.yml
• .github/workflows/deploy-production.yml
• .github/workflows/documentation.yml
• .github/workflows/eval.yml
• .github/workflows/publish.yml
• .github/workflows/verify-semver-label.yml

Release v0.2.1

Summary

A pull request from a fork cannot cut a release, and the run reports success anyway — so a merged, labeled contribution silently publishes nothing.

Added

• A check requiring exactly one major, minor or patch label before a pull request can be merged.

Changed

• Releases are cut on push to main instead of on the pull request closing, so contributions from forks publish like any other.
• The Publish run now fails when a merge releases nothing because the version label was missing, instead of reporting success.

Release v0.2.0

Summary

Prompter now moves work between Discord and the Cratis issue trackers, in both directions.

Added

• /issue turns a Discord conversation into a GitHub issue on the owning repository — bugs, missing APIs, feature requests, ideas, documentation gaps — drafted by Prompter and filed only after you confirm an ephemeral preview (P-45).
• Newly-opened issues get a grounded answer with citations on repositories that opt in, and silence when the documentation cannot answer them (P-44).
• New issues are announced in a maintainer channel with whether the documentation already answers them (P-46).

Release v0.1.1

Summary

The published image can now be pulled and started.

Fixed

• Container image builds again: it named a .NET 10 runtime tag that does not exist, so the first release published no image at all (P-26).

Release v0.1.0

No container image was published for this version — the build failed on a runtime base image that does not exist. Use v0.1.1 or later.

Summary

Prompter's first release: the bot can now be deployed to the Cratis UpCloud Kubernetes cluster from a released version.

Added

• Pulumi stack running Prompter on the existing UpCloud Kubernetes cluster: namespaced workload, in-cluster Postgres with pgvector, and an ingress publishing only POST /reindex (P-21).
• Deploy - Production workflow that pins the released image tag, applies the stack, and redeploys or rolls back any version on demand (P-21).

Changed

• Publish now deploys the version it just pushed, and skips cleanly while the cluster side is unconfigured (P-21).
• Deployment runbook documents how a release is actually cut: a merged pull request labeled major, minor or patch, or a manual dispatch with an explicit version (P-26).