Tags give the ability to mark specific points in history as being important
-
v3.1.1-rc3
Release: code-executor-mcp v3.1.1-rc35c55f6a0 · ·Release-candidate for 3.1.1 — exercises the automatic published-artifact version gate. Not a release.
-
v3.1.1-rc2
Release: code-executor-mcp v3.1.1-rc20e6dec44 · ·Release-candidate for 3.1.1 — second attempt, with the verifier argument parsing fixed. Not a release.
-
v3.1.1-rc1
7559f0ca · ·Release-candidate for 3.1.1 — validates the verify-before-publish gate on a real tag pipeline. Not a release.
-
v3.1.0
Release: code-executor-mcp v3.1.0ff722176 · ·v3.1.0 — Homebrew packaging (repo side) The HTTP server now obtains its own bearer token from the 0600 token file when none is supplied via the environment, so the packaged brew services path runs with auth ON without a per-machine secret in a static plist. ~/.code-executor/mcp.json becomes the canonical downstream-config location.
-
v3.0.4-rc2
Release: code-executor-mcp v3.0.4-rc25ef4252b · ·Release-candidate tag re-validating the v* release pipeline after the version-guard extension (issue #2). Not a shipped release.
-
v3.0.4-rc1
Release: code-executor-mcp v3.0.4-rc11eb37fa6 · ·Release-candidate tag validating the new v* release pipeline (issue #2). Not a shipped release.
-
-
-
-