Release based on pushed tag instead of hardcoded nightly tags#1
Merged
Conversation
Co-authored-by: fengqi-dev <10048504+fengqi-dev@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update workflow to publish based on tag
Release based on pushed tag instead of hardcoded nightly tags
Mar 2, 2026
There was a problem hiding this comment.
Pull request overview
Updates the release workflow so GitHub Releases are created using the pushed tag name (instead of hardcoded nightly tags), enabling tag-based versioning for published tarball artifacts.
Changes:
- Consolidates two separate release publishing steps into a single release publish step.
- Uses
${{ github.ref_name }}for both release name and tag name. - Publishes both VS Code and Cursor tarballs (and SHA256SUMS) under the same tag-named release.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+36
to
41
| - name: Publish release | ||
| uses: softprops/action-gh-release@v2 | ||
| with: | ||
| name: vscode-nightly | ||
| tag_name: vscode-nightly | ||
| name: ${{ github.ref_name }} | ||
| tag_name: ${{ github.ref_name }} | ||
| target_commitish: ${{ github.sha }} |
There was a problem hiding this comment.
workflow_dispatch can be run from a branch (e.g., main), and with the current config that would attempt to create/update a release tagged main. If the intent is “releases are only created for tags”, add a guard (e.g., if: startsWith(github.ref, 'refs/tags/')) on the publish step/job, or require an explicit tag input for workflow_dispatch and use that for tag_name/name.
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.
Workflow always published to fixed
vscode-nightly/cursor-nightlyreleases regardless of the triggering tag, making tag-based versioning impossible.Changes
Publish releasestep${{ github.ref_name }}— pushingv1.0.0creates av1.0.0releaseprerelease: trueso releases are stable by default✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.