Skip to content

v3.45.1

A security fix, plus project bookings from the MCP server, a fix for project requirements across groups, and the quick deploy logos.

  • Security: a credential could be exposed to signed-in users on installations set up with the Kubernetes installer. It is fixed in this version. If you run such an installation, upgrade, and follow the guidance we have sent you: upgrading alone does not replace the credential.
  • One group that required a project forced projects on all groups. A user in several groups on a queue was refused booking without a project if any of them required one. A project is now required only when every group the user has on the queue requires it, and the project picker follows the same rule.
  • The MCP server could not book on a project, so booking failed on a queue that requires one if the user had no default project. A new list_projects tool lists your projects and wallets, and create_job and check_availability take a project_id, priced on that project.
  • The logos in quick deploy and in emails were broken. Quick deploy now loads them from your own installation, so they also show where the public site cannot be reached.
  • The MCP server’s job details no longer include network internals that only the interface needs, which made each service three times as long for an agent.
  • check_availability reports the start cost separately (start_cost), and cost_per_minute is now what the job costs while it runs. It used to spread the start cost over the job’s length, which made a short job look several times more expensive per minute. total_cost is unchanged and was always right.