Repository navigation
feat: replace prescribed versions with the registry rule and drop the site - #13
Merged
Merged
Conversation
… site Record astroc4 and refresh every moved repository in the organisation snapshot, and correct the claim that the portal reads a project's site configuration. State the version rule the playbook was missing: an application takes the latest version its runtime supports, a published component declares the lowest version that compiles and passes per target framework, and a page shows a registry badge rather than a number that is wrong within a release. Add the purview-component-compatibility skill: the golden rule, the Purview component hierarchy as read from the registry, and a zero-dependency script that prints each dependency group so a floor is read rather than remembered. Remove the documentation site entirely. The wiki is plain Markdown, the portal publishes it from the catalogue entry, and no repository carries a site configuration: the configuration file, its template and the wiki index page are deleted. Bump TUnit, the telemetry generator and the pipeline tool to their current releases so the repository still demonstrates what it documents.
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.
Summary
Brings the playbook up to date with the organisation as it is today, and fixes two things the pages got wrong.
The organisation snapshot is current again
astroc4was missing entirely, and six repositories had moved since the last harvest.gh;just org-inventoryreports no drift (17 public repositories).openapi-xmlcommentsnow has an entry, and the one repository without an entry is the catalogue itself.Versions are a rule, not a ledger
foundations/Dependency-Versions.md, stated as principle 11: an application takes the latest version its runtime supports; a published component declares the lowest version that compiles and passes, per target framework.Getting-Startedandtemplates/keep the shape (one property per family) and drop the version list.The documentation site is gone
mkdocs.yml,templates/mkdocs.ymlanddocs/wiki/index.mdare deleted, and every reference is removed: the wiki is plain Markdown,_Sidebar.mdis the navigation, and the portal publishes the folder from its catalogue entry. The falsetechdocs-corerequirement is replaced with how the portal actually publishes.New skill:
purview-component-compatibilityThe golden rule, the Purview component hierarchy read from the registry, and
scripts/dependencies.mjs(zero dependency) which prints each dependency group and its minimums per target framework.Verification
dotnet build: 0 warnings, 0 errorsdotnet test: 91 total, 86 passed, 0 failed, 5 pre-existing skipsjust lint-check: cleannode scripts/dependencies.mjs: exercised against five live packages, including thenet10.0-windowsgroup