Skip to content

chore(main): release jacobian 0.8.0 - #335

Merged
morluto merged 6 commits into
mainfrom
release-please--branches--main--components--jacobian
Aug 3, 2026
Merged

chore(main): release jacobian 0.8.0#335
morluto merged 6 commits into
mainfrom
release-please--branches--main--components--jacobian

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.8.0 (2026-08-03)

Features

  • benchmarks: add task-scoped Harbor gates (a68b43e)
  • storage: remove retired workspace schema (8f6dc25)

Bug Fixes

  • address lifecycle, Lean, and Harbor review findings (e254903)
  • benchmark: accept positive denominator factors and bound evidence (11c7ac0)
  • benchmark: accept semantic frozen API scope wording (981b4a4)
  • benchmark: align continuant schema and refresh verifier checksum (ae58f2e)
  • benchmark: allow independently checkable irreducibility certificates (c550df1)
  • benchmark: bind convergence scope to Lebesgue semantics (84aab8a)
  • benchmark: bind indexed evidence and bound duplicate inputs (3c5ad74)
  • benchmark: bind infinite-spectrum evidence to all basis actions (70fe213)
  • benchmark: build research-status evidence semantics from prose only (949bee5)
  • benchmark: disclose result marker and catch nested JSON (13c1201)
  • benchmark: fail closed on malformed symmetric submissions (cb637e2)
  • benchmark: gate research-status-evidence-audit base reward on evidence, scope, and assurance (ed44019)
  • benchmark: harden convergence scope and parsing (b5bf476)
  • benchmark: harden projection scope and tail parsing (008a356)
  • benchmark: harden research-status-evidence-audit verifier (b9937df)
  • benchmark: make trigonometric derivation strategy agent-owned (6c6b87c)
  • benchmark: refresh research-status verifier checksum (8127e61)
  • benchmark: regenerate Harbor verifier checksum and dataset manifest for research-status-evidence-audit (71072a5)
  • benchmark: reject boolean continuant proof lengths (7a6e21b)
  • benchmark: reject negated symmetric scope claims (dc06808)
  • benchmarks: align Harbor job schema and digest (104d94b)
  • benchmarks: allow bounded agent networking without web search (b7108ef)
  • benchmarks: bind adapter evidence to checked results (5afdb15)
  • benchmarks: bind and bound research evidence (79d0e95)
  • benchmarks: bind snapshot provenance and retire stale research names (e3ef4e9)
  • benchmarks: complete research-status verifier review fixes (035cb21)
  • benchmarks: fail closed on malformed assurance claims (faeacb3)
  • benchmarks: fix import sorting in merged leaf tests and update complexity baseline (b62d286)
  • benchmarks: fix import sorting in test_exact_farkas_ldl_slice leaf file (13a1c38)
  • benchmarks: harden convergence evidence claims (b0c9c27)
  • benchmarks: keep Jacobian observations offline (45c4ff9)
  • benchmarks: match lowercased evidence term in inseparable-polynomial verifier (9c0e83c)
  • benchmarks: refresh Harbor adapter digest (fe22e54)
  • benchmarks: refresh stale symmetric divisibility verifier checksum (84710ff)
  • benchmarks: require integral divisibility multipliers (fca3890)
  • benchmarks: ruff format fixup (5b9fec2)
  • benchmarks: sync vendored verifier support to canonical source (00044b2)
  • benchmarks: update Farkas verifier checksum after ruff format (9151005)
  • benchmarks: update gap count, fix lint, update complexity baseline (fd0dd0e)
  • ci: accept valid irreducibility strategy (091631d)
  • ci: close planner review gaps (ea187ab)
  • ci: keep timing artifact failures out of test gates (5205fd9)
  • ci: pass PATHS through temporary files (35dee17)
  • ci: route test-changed through PATHS file (c935497)
  • ci: sync symmetric verifier support (ac4d66d)
  • ci: sync vendored Harbor verifier support (058ff8b)
  • ci: sync vendored Harbor verifier support (357b90c)
  • fail-closed JSON type checks for indexed pairwise vacuity verifier (29d96c4)
  • harbor: make Codex evaluations proxy-aware (f8bd184)
  • release: sync MCP package metadata versions (9b9d9d5)
  • security: update cryptography lock entry (e0b9b75)
  • storage: handle foreign keys during workspace removal (6d0cd7a)

Dependencies

Documentation

  • add Simplified Chinese README (#400) (94d02bc)
  • benchmarks: publish research-status scope (203302e)
  • simplify capability result guidance (7b6e7cb)
  • skills: add verifier evaluation guidance (7508f5a)
  • skills: clarify agent-facing eval contracts (be9c9cc)
  • streamline focused validation guidance (afff87b)
  • workflow: remove mandatory capability development path (3aea2dc)

This PR was generated with Release Please. See documentation.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 091bbcfdc3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread server.json Outdated
"source": "github"
},
"version": "0.7.0",
"version": "0.7.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Publish the matching npm package version

For the 0.7.1 release, this line moves the MCP server metadata to 0.7.1 but the same server.json still declares packages[0].version as 0.7.0. The publish-mcp workflow checks out this immutable release commit and publishes this metadata, so MCP Registry installers will be told to run the old npm package even though the registry entry is 0.7.1, skipping the 5205fd9 fix for registry consumers. Update the package entry to 0.7.1 together with the top-level version.

Useful? React with 👍 / 👎.

@github-actions github-actions Bot changed the title chore(main): release jacobian 0.7.1 chore(main): release jacobian 0.8.0 Aug 2, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--jacobian branch 2 times, most recently from f61d83d to c91f7ee Compare August 2, 2026 18:09

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 34a4aa1b5b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread server.json
"source": "github"
},
"version": "0.7.0",
"version": "0.8.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Publish the 0.8.0 package in registry metadata

Fresh evidence: this 0.8.0 bump changes only the server metadata version while packages[0].version remains 0.7.0; the release workflow checks out this immutable release SHA and then runs ./mcp-publisher publish, and the MCP versioning guidance says local server/package versions should align (https://modelcontextprotocol.io/registry/versioning#align-server-version-with-package-version). For this release, MCP Registry consumers will still be given jacobian@0.7.0 even though the Python and npm packages are 0.8.0, so registry installs miss the new release’s fixes.

Useful? React with 👍 / 👎.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--jacobian branch 9 times, most recently from d32a9da to a98092b Compare August 3, 2026 13:45
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--jacobian branch from e0f19a2 to c457497 Compare August 3, 2026 22:04
@morluto
morluto merged commit baa158f into main Aug 3, 2026
32 checks passed
@morluto
morluto deleted the release-please--branches--main--components--jacobian branch August 3, 2026 22:11
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant