2.43.1 — Targets Portainer 2.43.x
Added
- New
GITOPSprofile (#74) bundling thegitopstag — register/list/test
git sources and browse refs (the GitOps source management surface). - JMESPath errors now diagnose double-escaped quotes. When a
select
expression fails to parse and contains literal\"(the JSON-in-JSON
double-escaping models fall into), the error names the cause and suggests
plain double quotes or acontains(...)filter instead of the lexer's
opaqueUnknown tokenmessage. - Hygiene guide: four field-tested additions from agent usage reports — the
backslash-escaping trap and itscontains()workaround; the400 … EOF
rejection when a write call sends zero body fields (e.g. a bare
StackGitRedeploy— passPrune: false); verifying a K8s deploy end-to-end
via the service-proxy path; and whichStackCreateKubernetesGitfields are
the blessed path (SourceID) vs the still-functional deprecated inline
Repository*fields.
Changed
gitopsis now in the default profile set (#74). A
registered GitOps source is required to deploy a git-backed stack, sogitops
now rides along inside bothDOCKERandKUBERNETES(next tostacks) and
the defaultPORTAINER_PROFILESbecomesBASE,DOCKER,KUBERNETES,GITOPS.
Without it, git-based stack deploys fail for lack of a source.
Full changelog: https://github.com/portainer/portainer-mcp/blob/2.43.1/CHANGELOG.md