Repository navigation
Thu blog: deprecation and revocation leave the contract in place - #146
Merged
Merged
Conversation
Add the October 8 explainer and three long-tail Q&As on exact pins, host status signals, and how an agent should treat a revoked version at discover time. Wire them into the blog index, questions index, and llms.txt without changing the published embedder pin. Co-authored-by: Enrico Piovesan <enricopiovesan@users.noreply.github.com>
Bring in website#140 (embedder-web ^0.14.0) and website#147 (native package status) before the Thursday lifecycle truth-pass. Co-authored-by: Enrico Piovesan <enricopiovesan@users.noreply.github.com>
registry#631 is closed (fix registry#632). Exact pins in published traverse-registry 0.27.0 return lifecycle status; range resolution still skips deprecated and revoked. Runtime refusal stays open on traverse#1598, and v0.14.0 still pins =0.25.0. Native embedders match the published Maven, nuget, and swift-host package facts. Co-authored-by: Enrico Piovesan <enricopiovesan@users.noreply.github.com>
The shared-logic answer still described mobile hosts as in-tree only. Co-authored-by: Enrico Piovesan <enricopiovesan@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.
Ready for the CEO to merge. Do not merge from this branch automatically.
Truth-pass for 8 October 2026. The Thursday post and the lifecycle Q&As no longer say crates.io is stuck on
traverse-registry0.25.0 or that registry#631 is open.What changed
main(website#140 embedder pin^0.14.0, website#147 native package status).traverse-registry0.27.0 (crates.io, tagv0.27.0, 8 October 2026). Exact-pin resolution returns deprecated and revoked records with lifecycle status and revocation so the consumer can fail closed. Range resolution still skips both. Spec 005 FR-004 and decision 127 Q11. Fix merged as registry#632. registry#631 is closed.traverse-clirefusal ofrevokedis still traverse#1598, open, not in v0.14.0. Traverse v0.14.0 still pins=0.25.0. Enrico's comment on #1598 says the consumer slice can leave that pin.swift-host-v*tags (currentlyswift-host-v0.14.0-4), Kotlincom.traverse-framework:traverse-embedder0.14.0 on Maven Central, .NETTraverseEmbedder0.14.0 on nuget.org. Published, pre-1.0, not Certified.deprecated.jsonfiles on registrymain, zerorevoked.json. Live catalog: 227 entries, 38deprecated: true,revokedfalse on every entry./discoverstill skipsdeprecated: trueonly.URLs
Commits
2b74fcdmergeorigin/main671a5dftruth-pass to 0.27.0289cb7dnative embedder wording on the shared-logic Q&A