Repository navigation
Publish spike branches to the GitHub Packages feed with sortable versions - #1045
Open
FreeApophis wants to merge 2 commits into
Open
FreeApophis wants to merge 2 commits into
FreeApophis wants to merge 2 commits into
Conversation
…ions The nightly workflow also runs on spike/** branches, labels their packages after the branch (spike-traits.20261030.12 next to nightly.20261030.12) and uses a date plus the run number as the suffix, so the versions sort chronologically; the commit stays in the Source Link metadata. The SDK step matches build.yml. The repository URL is given without the .git suffix so that GitHub Packages links the packages to this repository. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…d into the previous commit Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
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.
Groundwork for the 4.0.0 spikes (#862, #1034): their packages should be testable from the polyadic GitHub Packages feed, next to the nightlies. Independent of the open 4.0.0 chain.
publish-nightly-package.ymlalso triggers onspike/**branches. A spike's packages carry the branch as prerelease label (spike/traits→4.0.0-spike-traits.20261030.12), main keepsnightly.<label>.<yyyyMMdd>.<run number>instead of the short commit hash, so NuGet orders the versions and--prereleasepicks the newest; the commit is in the package's Source Link metadata.build.yml, instead of "the current SDK".Directory.Build.propssetsRepositoryUrlwithout the.gitsuffix (Source Link still fills commit and branch). GitHub only links a package to a repository when the nuspec URL matches exactly, which is why the nightlies show up under the organization but not in the repository sidebar. Verified in a local pack:<repository type="git" url="https://github.com/polyadic/funcky" branch="…" commit="…" />.The feed stays https://nuget.pkg.github.com/polyadic/index.json; consuming it needs a token with the packages read scope.
🤖 Generated with Claude Code