Repository navigation
docs(roadmap): the largest unknown in the release was measured six days ago - #109
Merged
Merged
Conversation
…ys ago This page describes the Mac App Store runtime as an open question and counts two requirements open against it. F8 was updated a day later and says the opposite: the interpreter was signed into a minimal bundle with the store lane's sandbox entitlements and asked about itself on 2026-09-07, every capability the product needs works sandboxed, the runtime change has been made, and F8-R28 is satisfied. The page warns in its own words that it was the stale one before. It was again, and about the item it nominated as the biggest risk in the release -- which reads to a planner as engineering work outstanding when what is left is a provisioning profile and a certificate from the Apple Developer portal. Signed-off-by: Wessel Verheij <info@nightworks.io>
|
github-actions
Bot
added
documentation
github-actions
Bot
added
awaiting-maintainer
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.
The app-store section describes the Mac App Store runtime as an open question —
"It is the largest unknown in this release" — and counts two F8 requirements
open against it.
F8 was
updated a day after this page and says the opposite. The interpreter was signed
into a minimal bundle with the store lane's sandbox entitlements and asked about
itself on 2026-09-07, each probe run twice so a failure reproducing outside the
sandbox could not be mistaken for one caused by it:
224.0.0.251:5353The runtime change has since been made — a
mastarget with its ownentitlements pair and the interpreter relocated into
Contents/MacOS— soF8-R28is satisfied. F8 carries no open marker.This matters beyond tidiness: the page nominates this item as the biggest risk
in the release, so a planner reads engineering work outstanding where what is
actually left is a provisioning profile and a Mac Installer Distribution
certificate from the Apple Developer portal. The page warns in its own words
that it was the stale one before; it was again, and about the item it had
singled out.
Gates run locally:
integrity.pyclean,manifest_check.pyclean (1 manifest,373 goals). No requirement text, id or manifest goal changed — this edits
narrative only.