Simplify SPM publish workflow and add explicit SPM versioning guidance - #27
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Update workflow and README with SPM versioning guidance
Simplify SPM publish workflow and add explicit SPM versioning guidance
Jul 28, 2026
There was a problem hiding this comment.
Pull request overview
This pull request updates the SPM manifest publishing workflow to remove workflow-driven PR automation while keeping the existing release-asset-based manifest rendering and branch publishing behavior. It also updates the README to give clearer guidance on how to pin stable vs prerelease versions when consuming the SDK via Swift Package Manager.
Changes:
- Removed
pull-requests: writepermission and deleted allgh pr create/edit/listautomation from the publish workflow. - Changed the workflow’s version/branch derivation to use the release tag as-is (
VERSION="$TAG"), and added a final step that prints a manual compare URL for PR creation. - Updated README SPM guidance with
from(stable) andexact(prerelease) examples.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| README.md | Updates SwiftPM consumption guidance with stable vs prerelease pinning examples. |
| .github/workflows/publish-spm-manifest.yml | Simplifies release publish flow by removing PR automation and using tag-as-is for branch derivation, with a manual PR handoff URL. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
SaBhandari91
marked this pull request as ready for review
July 28, 2026 15:09
SaBhandari91
enabled auto-merge (squash)
July 28, 2026 15:10
SaBhandari91
approved these changes
Jul 28, 2026
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (2)
README.md:34
- The prerelease example uses
exact: "5.0.0-beta-01", but the repo’s current prerelease tag includes a leadingv(e.g.v5.0.0-beta-01). If readers copy/paste this, SPM won’t find the tag. Align the example with the actual tag name (or clarify that users must match the tag string exactly).
.package(url: "https://github.com/microsoftconnect/Dragon-Copilot-UI-SDK-iOS", exact: "5.0.0-beta-01")
README.md:30
- The README example uses
from: "5.0.0", but this repo’s current stable tag format appears to be4.0.0(and there is no5.0.0tag at the moment). Using a non-existent version in the primary example will cause SPM resolution to fail for readers who copy/paste it. Consider updating the example to an existing stable tag (or make it a placeholder like"<latest-stable>").
.package(url: "https://github.com/microsoftconnect/Dragon-Copilot-UI-SDK-iOS", from: "5.0.0")
sagarmahewar-stack
approved these changes
Jul 30, 2026
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.
This updates the SPM manifest publish flow to stop workflow-managed PR operations while preserving manifest generation/push behavior on release events. It also clarifies README guidance for stable vs prerelease SPM dependency pinning.
Workflow: remove PR automation, keep release branch publishing
release.published.gh pr create/edit/listlogic entirely.release/<tag>, now derived directly from the tag (VERSION="$TAG").Workflow: least-privilege permissions + manual PR handoff
contents: writeonly.https://github.com/$GITHUB_REPOSITORY/compare/main...$BRANCH?expand=1Workflow: tag handling
v-prefix enforcement.README: SPM versioning guidance
fromexact