Skip to content

chore: publish accumulated main changes - #2

Open
Oneiros667 wants to merge 1 commit into
mainfrom
codex/publish-main-20260917
Open

Oneiros667 wants to merge 1 commit into
mainfrom
codex/publish-main-20260917

Conversation

@Oneiros667

Copy link
Copy Markdown
Owner

Summary

  • Publish the complete local main tree through the protected main branch workflow.
  • Flatten the unpublished history into one linear commit so it complies with the no-merge-commits rule.
  • Preserve the exact local main tree; local main remains unchanged.

Verification

  • .NET restore, build, tests, and format check passed.
  • Python: 257 tests passed; Ruff and deterministic MCP fixture evaluation passed.
  • Markdown lint, publication safety, workflow, conventional-commit, and whitespace checks passed.
  • Six .NET tests skipped because MongoDB, Neo4j, Qdrant, and the optional sample configuration were unavailable.
  • Markdown-link check remains blocked by two pre-existing ignored CodeQL README links under .codemesh-evals.

Comment thread agent-access/codemesh_agent_access/cli.py Dismissed
Comment thread agent-access/codemesh_agent_access/cli.py Dismissed
Comment thread agent-access/codemesh_agent_access/cli.py Dismissed
Comment thread agent-access/codemesh_agent_access/cli.py Dismissed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants