Skip to content

ci(publish): pack ANcpLua.Agents.Hosting.BitNet on alpha channel#83

Merged
github-actions[bot] merged 2 commits into
mainfrom
fix/bitnet-publish-pack-step
May 13, 2026
Merged

ci(publish): pack ANcpLua.Agents.Hosting.BitNet on alpha channel#83
github-actions[bot] merged 2 commits into
mainfrom
fix/bitnet-publish-pack-step

Conversation

@ANcpLua
Copy link
Copy Markdown
Owner

@ANcpLua ANcpLua commented May 13, 2026

Summary

  • PR feat: ANcpLua.Agents.Hosting.BitNet runtime package + source generator #77 introduced the ANcpLua.Agents.Hosting.BitNet runtime package but never appended it to the alpha-channel pack step in nuget-publish.yml. Every release since v1.4.8 shipped the other Hosting.* siblings (Anthropic / Azure / DevUI / Foundry preview, OpenAI alpha) while BitNet stayed dark on nuget.org — nuget.org/packages/ANcpLua.Agents.Hosting.BitNet still returns 404.
  • Consumers (qyl, others) pin a 1.4.x-alpha.1 BitNet version that has never been published, so dotnet restore fails with NU1101: Unable to find package ANcpLua.Agents.Hosting.BitNet.
  • Channel choice: Hosting.BitNet.csproj self-declares "Alpha-channel BitNet (bitnet.cpp llama-server) hosting facades…" and wraps an experimental runtime, so it joins the -alpha.1 suffix alongside Hosting.OpenAI rather than the -preview.1 train.
  • Trusted publishing: the existing owner-scoped ANcpLua.Agents*Agents.Testing, Workflows policy (Owner=ANcpLua, Repo=ANcpLua.Agents, Workflow=nuget-publish.yml, Environment=nuget) already authorizes any ANcpLua-owned package, so no per-package policy is required.

After this merges to main, the next auto-bumped tag (v1.4.10v1.4.9 is the latest tag and HEAD has commits past it) will ship ANcpLua.Agents.Hosting.BitNet 1.4.10-alpha.1.

Test plan

  • CI passes on Linux / Windows / macOS build matrix
  • Linux pack step produces artifacts/ANcpLua.Agents.Hosting.BitNet.<version>-alpha.1.nupkg and .snupkg
  • Must Publish Packages gate detects the src/** change since v1.4.9 and proceeds to publish
  • NuGet/login@v1 issues a short-lived OIDC API key — push step authorizes BitNet via the owner-scoped policy
  • https://www.nuget.org/packages/ANcpLua.Agents.Hosting.BitNet 200s with the new version after propagation
  • Consumer qyl (Version.props pin bumped to 1.4.10-alpha.1) restores without NU1101

Summary by CodeRabbit

  • Chores
    • Updated the NuGet publish workflow to include the BitNet hosting package in the alpha channel releases alongside existing packages.

PR #77 introduced the runtime package but never appended it to the
alpha-channel pack step in nuget-publish.yml, so every release since
v1.4.8 shipped the other Hosting.* siblings while BitNet stayed dark
on nuget.org. Consumers pin a BitNet version that does not exist and
restore fails with NU1101.

Channel choice: BitNet's csproj Description self-declares "Alpha-
channel" and wraps the experimental bitnet.cpp llama-server runtime,
so it rides the same -alpha.1 suffix as Hosting.OpenAI rather than
the -preview.1 train.

Trusted publishing is already covered by the existing owner-scoped
ANcpLua.Agents policy on nuget.org (no per-package policy needed).
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e996cfa4-a2d1-4da7-ba1e-843daf400b23

📥 Commits

Reviewing files that changed from the base of the PR and between 696acb0 and b6c9bf9.

📒 Files selected for processing (1)
  • .github/workflows/nuget-publish.yml
📜 Recent review details
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: build (windows-latest)
  • GitHub Check: build (macos-latest)
  • GitHub Check: claude-review
🧰 Additional context used
📓 Path-based instructions (1)
.github/workflows/**

⚙️ CodeRabbit configuration file

.github/workflows/**: Pin third-party actions to SHA. First-party (actions/*) tag-pin OK.
Concurrency groups required on push-triggered workflows.
Secrets via env: not inline. No secrets in logs.
Tag-with-gate pattern: nuget environment requires manual approval.

Files:

  • .github/workflows/nuget-publish.yml
🔇 Additional comments (1)
.github/workflows/nuget-publish.yml (1)

116-122: Alpha channel pack step update is correct and policy-compliant.

Adding ANcpLua.Agents.Hosting.BitNet to the alpha pack block is the right fix for the release gap, and it preserves the existing gating/publish flow without introducing workflow policy violations.


📝 Walkthrough

Walkthrough

The NuGet publish workflow in .github/workflows/nuget-publish.yml was updated to include an additional package in the alpha channel. The alpha packaging step now runs dotnet pack for both the existing OpenAI hosting project and the new BitNet hosting project (ANcpLua.Agents.Hosting.BitNet) with the same -alpha.1 version suffix. Both resulting .nupkg artifacts are subsequently uploaded and published under the existing artifact and publish gates.

🚥 Pre-merge checks | ✅ 9
✅ Passed checks (9 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed Title follows conventional commits format (ci scope), is under 72 characters (64), has no trailing period, and accurately describes the main change: adding BitNet hosting package to alpha channel.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
No Datetime.Now/Utcnow ✅ Passed No DateTime.Now/UtcNow usage found in C# code. PR modifies only nuget-publish.yml workflow file to add BitNet packing to alpha channel.
No .Result/.Wait() Blocking Async ✅ Passed No C# files were added or modified in this PR. Only .github/workflows/nuget-publish.yml (YAML) was changed. Check is not applicable to non-C# files.
No Null-Forgiving Operator Without Justification ✅ Passed No C# files modified. PR only changes .github/workflows/nuget-publish.yml (YAML). Check for C# null-forgiving operators is not applicable.
Suppressions Limited To Meai001/Openai002 ✅ Passed PR modifies only .github/workflows/nuget-publish.yml (CI workflow file). No C# files are added or modified. Therefore, no warning suppressions can be present. Check requirement not applicable.
No Preview-Type Leak Into Stable Surface ✅ Passed PR modifies only .github/workflows/nuget-publish.yml (CI workflow). No C# source files in src/ANcpLua.Agents/ were added or modified. Check is N/A.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

@coderabbitai autofix

@claude
Copy link
Copy Markdown

claude Bot commented May 13, 2026

Claude encountered an error —— View job


I'll analyze this and get back to you.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

@github-actions github-actions Bot enabled auto-merge (squash) May 13, 2026 02:36
@github-actions
Copy link
Copy Markdown

@coderabbitai autofix

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

@github-actions github-actions Bot merged commit 2f0f882 into main May 13, 2026
9 checks passed
@ANcpLua ANcpLua deleted the fix/bitnet-publish-pack-step branch May 16, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant