Add ReactiveProperty release skill#558
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
Adds a contributor-facing skill for ReactiveProperty releases so agents follow the repository's current tag-driven NuGet publishing flow. This captures the release runbook in
.agents/skills/instead of treating it as a consumer-facing ReactiveProperty skill.The skill covers release mode selection, version/tag validation, target commit preflight, local validation, tag push confirmation, GitHub Actions monitoring, and NuGet/GitHub Release verification. It also documents that version bump PRs are optional record-keeping only for the current workflow because package versions are derived from the
v*tag during release.Notes
The pre-release path requires
-prein the version because the current workflow uses that substring to mark GitHub Releases as prerelease.Validation
ask_userguard, pre-release/stable mode coverage, error handling, output format, and post-run reflection.