release: bump to 0.14.2 - #28
Merged
Merged
Conversation
Ships the documentation already on main. The package carries README.md and docs/ inside the tarball, and npmjs.com renders that README, so the fix for #22 does not reach a reader until a release goes out. Published 0.14.1 still shows the model example addressing runtime.ref(Cart, ...) under createRuntime, which throws, and says nothing about a process that installs and then waits claiming no work. That README is the artifact the original report was about. No runtime code changed. The Unreleased section becomes 0.14.2, dated, because the publish job reads that section to build the release notes.
Greptile SummaryThis release-only PR publishes the documentation and example improvements already merged for version 0.14.2.
Confidence Score: 5/5The PR appears safe to merge with all release version identifiers synchronized. The package version, exported runtime version, and changelog release heading agree on 0.14.2, and no runtime logic or security boundary changes. Important Files Changed
Reviews (1): Last reviewed commit: "release: bump to 0.14.2" | Re-trigger Greptile |
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
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.
Documentation-only release. No runtime code changed.
Why now
The package ships
README.mdanddocs/inside the tarball, and npmjs.comrenders that README. The fix for #22 merged in #27, but published 0.14.1 still
shows the broken guidance:
That is the exact page the external prober read before concluding messages
were stranded, so leaving it unpublished leaves the report unaddressed for
anyone arriving through npm. The gem does not have this gap: solid_objects
0.14.1 shipped its equivalent docs fix on RubyGems.
What ships
run(signal)statement inREADME.mdanddocs/operations.md(docs: state that background pickup requires runtime.run(signal) #22).configure()and addressed asCart.ref("cart-123"), which is the form that actually runs.examples/at-least-onceandpnpm run test:at-least-once(examples: make the at-least-once duplicate observable at a sink with dedup off #23).Verified in the packed tarball rather than the working tree:
Validation
Full release gate list from
docs/releasing.md, all passing locally:format:check,check,test:coverage,build,pack:check,test:package,test:recovery,test:at-least-once,pnpm audit --audit-level=high(no known vulnerabilities), andtest:browser(9 passed). The PostgreSQL, MySQL, and Redis matrices run herein CI.