Repository navigation
Release 1.2.11: fix Moonraker authentication and Bambu interoperability - #31
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Released as 1.2.11. The missing npm trusted publisher is configured for this repository’s publish.yml workflow, and publication attempt 2 succeeded with signed provenance. Remote main, the v1.2.11 tag and npm gitHead all match c614529. A fresh npx install reports 1.2.11, discovers 30 MCP tools and initializes successfully without printer actions. Main CI and Pages deployment passed; the live changelog shows the dated released version. Full tests: 462 passed, two optional installed-profile checks skipped, zero failures. Loopback transport and isolated Blender checks passed; no physical print or user scene mutation was performed. Original contributor commits are preserved, credits are recorded, and Jack’s contribution is acknowledged on #30. |
Moonraker hosts requiring authentication currently return 401 because the configured API key is omitted. Integrate Jack Manning’s #30 with loopback regressions covering all nine authenticated and anonymous request paths. Preserve its original commit and the MCP Registry metadata contribution from #28.
Release 1.2.11 also ports the fork’s corrected fresh A1/A1 mini identity and bounded M109 H wait support, keeps parsing/slicing/STL diagnostics off MCP stdout, and replaces the remaining directory-creating Bambu file lookup with read-only FTPS. Remove obsolete bambu-js and update compatible runtime dependencies; production audit is clear. Preserve the A1 compatibility contributor’s code authorship and credit the reports in CONTRIBUTORS.md.
Package/lockfile/Registry versions agree. The dated changelog includes validation limits and clearly identifies the earlier 1.2.10 batch as unpublished on npm; this release includes that batch. Registry submission is not claimed by this metadata preparation.
Validation: zero TypeScript errors; 462 full-suite tests passed, 2 optional installed-profile checks skipped; 16 behavior tests passed; packed installation/MCP startup passed on all three entrypoints; docs site built; official Registry schema validated. Upstream mcp-for-blender 2.1.9 and blender-mcp 2.0.0 both passed discovery, invocation and a 12-triangle 40×20×10 mm STL export in isolated Blender 5.0.1. No physical printer or user scene was touched. Local Standards/Spec review found no blocking findings; minor header duplication and development-only watcher advisories are deferred.
After current-head CI and merge: verify trusted npm publication, matching tag/release, fresh npx startup and live Pages changelog. The previous 1.2.10 publication failed with npm E404; publication must be verified rather than assumed.