release: bump public packages to 1.1.0 - #263
Merged
Merged
Conversation
Lockstep bump of every public package from 1.0.1 to 1.1.0. Files the 1.1.0 changelog and backfills a short 1.0.1 section for the already shipped patch. Unreleased is empty of list items. This PR does not publish to npm. After merge, run `pnpm publish:dry`, then `pnpm publish:ci` from the release commit. That command now tags `v1.1.0` and opens the GitHub release from the filed CHANGELOG.md section (#261). ## 1.1.0 - `flatbread proof write` now accepts `Retract` (#260). Session noise and other records that should not stay on the live graph are tombstoned in place. Retract refuses a sole closer and the last live Finding on a realized Risk. Efforts cannot be retracted. - The Proof skill now applies a 4/4 write gate on creates and on body edits that add claims. - Proof read envelopes expose `complete` and `cap_reasons` (#254). `page.has_more` is pagination-only. An unpaired `hasMore` flag without a non-empty cursor is refused. - **Breaking for writes:** create-time `derives_from`, `supersedes`, and `invalidates` reject other-Effort targets (#253). Stored foreign edges report `PROOF_CROSS_EFFORT_RELATION`. - Docs use Proof as the product name, not "The Proof" (#259). - Brand marks land under `assets/brand/` (#256). - `pnpm publish:ci` creates the GitHub release from CHANGELOG.md after npm publish (#261). ## Checklist - [x] No new public exports - [x] Changes generate no new console errors - [x] Version and changelog only; no new tests required ### Does this introduce any non-backwards compatible changes? - [x] Yes — Proof write creates reject cross-effort relation targets - [ ] No ### Does this include any user config changes? - [ ] Yes - [x] No Change-Id: I9f1ff14ca6d25f1d267a70b37e101cf5be412c56 Co-authored-by: Tony <tonyketcham@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lockstep bump of every public package from 1.0.1 to 1.1.0. Files the 1.1.0 changelog.
npm 1.1.0 and the GitHub release https://github.com/FlatbreadLabs/flatbread/releases/tag/v1.1.0 are already published from
eb74911. This PR lands that bump onmain.Test plan
pnpm publish:drypassed oneb749111.1.0on npm (latest)v1.1.0is published and marked LatestMade with Cursor