Conversation
The package README on nuget.org is frozen per published version. This README is the one packed into Atypical.VirtualFileSystem (<None Include="../../README.md" Pack="true" /> in src/Atypical.VirtualFileSystem.Core/*.csproj:15), so the footer reaches the package page on the next release. Footer is byte-identical to the existing one in 38 other repo READMEs, same <!-- portfolio-nugetkeep:start --> markers and same UTM values. No copy changed. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This branch has not been deployed
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.
Why
A package's README on nuget.org is frozen per published version. The
portfolio-nugetkeepfooter exists in 38 repository READMEs but is only visible on 1 of 30 package pages on nuget.org (RoselineMCP, 1.2% of total downloads), because every other package last shipped before the footer landed.This repo was not one of the 38 — it had no footer at all.
What this changes
Appends the existing footer to
README.md, which is the file packed into theAtypical.VirtualFileSystempackage. Verified, not assumed:src/Atypical.VirtualFileSystem.Core/Atypical.VirtualFileSystem.Core.csproj:15→<None Include="../../README.md" Pack="true" PackagePath="" /><PackageReadmeFile>README.md</PackageReadmeFile>Atypical.VirtualFileSystem0.3.0 nuspec declares<readme>README.md</readme>The footer is byte-identical to the one in the other repos — same
<!-- portfolio-nugetkeep:start -->/:endmarkers, same UTM values (utm_source=github-readme&utm_medium=readme&utm_campaign=launch-2026-07). 316 bytes appended, no existing prose touched, no copy rewritten.The UTM values must stay exactly as-is:
utm_medium=readmeis what segments this channel in Umami. A drifted parameter silently destroys the channel's ability to report its own conversion rate.This does not publish anything
Merging this changes nothing on nuget.org. The footer only reaches the package page when a new version is published, and that is gated on Philippe's explicit approval.
Two things to know before any such release:
v*tag via.github/workflows/publish-to-nuget.yml, version derived from the tag.Directory.Build.props:13says<Version>0.5.0</Version>and tagv0.5.0exists, but nuget.org's latest is 0.3.0 — the v0.4.x/v0.5.0 tags did not publish. Worth understanding before tagging anything, or the next tag fails the same silent way.No version bump is included in this PR.
Part of ATY-50.