Repository navigation
Tags
Tags
Publish to nuget.org with trusted publishing The NuGet API key expired, so v1.0.0-beta.4 failed to push (403). The publish job now exchanges a GitHub OIDC token for a short-lived key with NuGet/login, as the user in vars.NUGET_OIDC (or secrets.NUGET_OIDC), in the nuget environment that the nuget.org policy for devlooped/stunts requires. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: CodeAlta <noreply@codealta.io>
Bump NuGetizer from 1.5.0 to 1.5.1 --- updated-dependencies: - dependency-name: NuGetizer dependency-version: 1.5.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Stop inlining expanded content in package readmes.
Make sure breakpoints on scenario source are active in debugging Previously, because we were loading the CS files from the output directory, the breakpoints set in the actual scenario source were not being picked-up by VS. By loading them from the actual source location in the project, breakpoints Just Work :D
Since we publish releases from ubuntu builds, use those for acceptance We were validating main builds using the windows-built bits (by uploading the pipeline artifacts from windows), but we were pushing for releases the bits from ubuntu. Make it consistent by unifying on ubuntu (which also happens to be the one that builds fastest, so...)