Repository navigation
Prepare 1.0.0-beta.3 release - #66
Merged
Merged
Conversation
Sync both version numbers to 1.0.0-beta.3. The app csproj was at 1.0.0-beta while the Aspire package was at 1.0.0-beta.2; they now move together so a tag names a single version across both artifacts. Add a NuGet publish workflow for F23.Aspire.Hosting.AzureSearchEmulator, which had no release automation. It triggers on the same v*.*.* tags as the Docker workflow and authenticates with NuGet trusted publishing (OIDC) rather than a stored API key, so no long-lived credential is needed. Requires a one-time trusted publishing policy on nuget.org naming this repo and nuget-publish.yml, plus a NUGET_USER secret holding the nuget.org profile name. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
paulirwin
force-pushed
the
prepare-1.0.0-beta.3
branch
from
August 31, 2026 21:33
7e355e1 to
ceb6789
Compare
The NuGet workflow only packed AzureSearchEmulator.Aspire, so the AzureSearchEmulator tool package - configured for packing in #80 but never added here - would not have shipped on the next tag. The push step already globs ./artifacts/*.nupkg, so packing both into the same directory is all that was needed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nopse51MyjYAUr4iCoh5wx
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.
Prepares the first tagged release of the project. There are currently no git tags and no GitHub releases, so this establishes the release path rather than following an existing one.
Version sync
Both
<Version>properties move to1.0.0-beta.3. They had drifted — the app csproj was at1.0.0-betawhile the Aspire package was at1.0.0-beta.2— so a single tag now names one version across both artifacts.Staying on the
1.0.0-beta.Nline rather than declaring 1.0.0: the emulator is still filling in API surface against real Azure AI Search, and anything still missing would become a semver-breaking fix later.NuGet publishing
F23.Aspire.Hosting.AzureSearchEmulatorhad no release automation at all — nothing packed or pushed it, so the published package has been stale at1.0.0-beta.2. The newnuget-publish.ymltriggers on the samev*.*.*tags as the existing Docker workflow.It authenticates with NuGet trusted publishing (OIDC) rather than a stored API key, so there is no long-lived credential in the repo.
id-token: writeis scoped to the publishing job only, and the login step sits immediately before the push because each OIDC token is single-use and the key it returns expires after an hour.Worth flagging for review: a widely-circulated blog post on this reads the key from
steps.login.outputs.api-key, which is wrong and silently yields an empty key. The correct output isNUGET_API_KEY, verified against the action's ownaction.yml.Required before the tag is pushed
Two one-time setup items that can't be done from the repo:
feature23, repositoryAzureSearchEmulator, workflow filenuget-publish.yml(filename only, no path), environment blank. Policies are owner-scoped, so this works even though the package has never been published from CI. A new policy is provisionally active for 7 days and only becomes permanent after one successful publish.NUGET_USERrepo secret — the nuget.org profile name, not an email address.Release notes
Separately from this diff, all 28 merged PRs have been labeled with
notes:*categories so.github/release.ymlsorts them properly — the 21 in this release plus 7 older ones that would otherwise have landed under "Other Changes".Verification
dotnet packproduces.nupkgand.snupkgat1.0.0-beta.3🤖 Generated with Claude Code