Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ All notable changes to Plainweave are documented here. The format follows

## [Unreleased]

## [1.2.0] — 2026-06-28

Closes the CLI/MCP parity gap for the 1.1 peer-facts producers (they shipped MCP-only).
Additive and backward-compatible; the new surfaces are advisory and verdict-free like the
rest of Plainweave.
Expand Down Expand Up @@ -101,5 +103,6 @@ coverage *completeness* remains a documented roadmap item, not a 1.0 gate.)
- Zero Plainweave-minted SEIs; sibling SEIs consumed opaquely.
- No silent-clean — a degraded or language-partial denominator is flagged in-band.

[1.2.0]: https://github.com/foundryside-dev/plainweave/releases/tag/v1.2.0
[1.1.0]: https://github.com/foundryside-dev/plainweave/releases/tag/v1.1.0
[1.0.0]: https://github.com/foundryside-dev/plainweave/releases/tag/v1.0.0
2 changes: 1 addition & 1 deletion src/plainweave/_version.py
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = "1.1.0"
__version__ = "1.2.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.

P2 Badge Update the deployed site for 1.2.0

When this release bump is tagged as v1.2.0, the package will report 1.2.0 but the public member site remains stale: I checked site/src/pages/index.astro, which still hard-codes VERSION = '1.0.0' and a hero note saying the snapshot is 1.1.0 untagged, and .github/workflows/site.yml only deploys on site/** changes. Because this commit changes only the package version/changelog, merging it leaves users seeing contradictory release information until a separate site change is made.

Useful? React with 👍 / 👎.

Loading