Changesets for 0.1.1 — ship the safety rule#20
Merged
Conversation
Four merged changes touch published packages and none carried a changeset — the process CONTRIBUTING requires and the author of those PRs (me) skipped. The material consequence: published 0.1.0 still lets a model invalidate true memories, because the safety rule from #12 never shipped. All four are patches. rememberMany is additive and would normally be a minor, but this project's roadmap reserves 0.2 for workspaces and the pre-1.0 minor lane is being used to signal breakage; the changeset says so, so the decision is recorded where the version bump is. Merging this lets the release workflow open the version PR for 0.1.1 — which is also the first live test of commitMode: github-api, the one piece of the release pipeline that has not yet run: the version PR's commit should arrive Verified and merge without an admin bypass.
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
1 participant
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.
Four merged changes touch published packages with no changeset — a process miss in my PRs (#10, #12, #14, #19). The one that matters: published 0.1.0 still lets a model invalidate true memories; the rule from #12 never shipped.
All four recorded as patches —
rememberManyis additive and would normally be a minor, but the roadmap reserves 0.2 for workspaces and pre-1.0 minors here signal breakage; the changeset records that reasoning next to the bump.Merging this starts the 0.1.1 train and live-tests the last unproven pipeline piece: the version PR that follows should carry a Verified commit (
commitMode: github-apifrom #9) and merge without the admin bypass 0.1.0 needed. If it doesn't, that's a finding too.