Skip to content

Create discussion and upload exe to beta/RCs#18732

Merged
seanbudd merged 3 commits intobetafrom
fixBetas
Aug 18, 2025
Merged

Create discussion and upload exe to beta/RCs#18732
seanbudd merged 3 commits intobetafrom
fixBetas

Conversation

@seanbudd
Copy link
Copy Markdown
Member

@seanbudd seanbudd commented Aug 18, 2025

Link to issue number:

Part of #18556

Summary of the issue:

Beta/RC tags do not upload the exe to the release assets, unlike stable releases.

Additionally, to make it easier to discuss issues with betas, creating a beta discussion is useful.
It also allows us to easily share each new release in slack and other places via Discussions RSS feed. The releases RSS feed includes tags, which duplicates posts to slack.

If a build fails due to system tests, you cannot rebuild it as the cache gets deleted.

Description of user facing changes:

None

Description of developer facing changes:

GitHub discussions are created for betas and RCs.
All releases are auto-posted to slack.
The installer artifact is uploaded to the release assets.

Description of development approach:

fix up action

only delete cache on successful build

Testing strategy:

Known issues with pull request:

Code Review Checklist:

  • Documentation:
    • Change log entry
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • API is compatible with existing add-ons.
  • Security precautions taken.

@coderabbitai summary

Copilot AI review requested due to automatic review settings August 18, 2025 02:09
@seanbudd seanbudd requested a review from a team as a code owner August 18, 2025 02:09
@seanbudd seanbudd requested a review from SaschaCowley August 18, 2025 02:09
@seanbudd seanbudd changed the base branch from master to beta August 18, 2025 02:09
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds discussion category support for prerelease uploads and introduces a new step to upload executable files to release assets for both beta/RC and stable releases.

  • Adds --discussion-category Releases flag to prerelease publishing to enable GitHub discussions
  • Introduces a new workflow step to upload exe files to release assets with clobber option

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

seanbudd and others added 2 commits August 18, 2025 12:10
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@SaschaCowley
Copy link
Copy Markdown
Member

@seanbudd none of the code review checklist items are ticked. Is this PR ready for review?

@seanbudd
Copy link
Copy Markdown
Member Author

Yep sorry

@seanbudd seanbudd enabled auto-merge (squash) August 18, 2025 04:45
@seanbudd seanbudd merged commit a27ac68 into beta Aug 18, 2025
81 of 84 checks passed
@seanbudd seanbudd deleted the fixBetas branch August 18, 2025 05:06
@github-actions github-actions bot added this to the 2026.1 milestone Aug 18, 2025
OzancanKaratas pushed a commit to OzancanKaratas/nvda that referenced this pull request Aug 18, 2025
Part of nvaccess#18556
Summary of the issue:

Beta/RC tags do not upload the exe to the release assets, unlike stable releases.

Additionally, to make it easier to discuss issues with betas, creating a beta discussion is useful.
It also allows us to easily share each new release in slack and other places via Discussions RSS feed. The releases RSS feed includes tags, which duplicates posts to slack.

If a build fails due to system tests, you cannot rebuild it as the cache gets deleted.
Description of user facing changes:

None
Description of developer facing changes:

GitHub discussions are created for betas and RCs.
All releases are auto-posted to slack.
The installer artifact is uploaded to the release assets.
seanbudd added a commit that referenced this pull request Aug 25, 2025
Fixup of #18732
Summary of the issue:

The release failed as we were unable to use a star import to upload release assets to GitHub

https://github.com/nvaccess/nvda/actions/runs/17196535198/job/48780625010
Description of development approach:

Get the name of the file before trying to upload it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants