Skip to content

chore: Fix release/pre-release Github workflow #517

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
colinmurphy merged 1 commit into from
Nov 20, 2025
Merged

chore: Fix release/pre-release Github workflow #517

colinmurphy merged 1 commit into from
Nov 20, 2025

Conversation

@colinmurphy
Copy link
Member

@colinmurphy colinmurphy commented Nov 20, 2025 •
edited
Loading

Description

Added a step to determine if the release is a pre-release or full release based on the version number. The release title and prerelease flag are now set dynamically, improving automation and reducing manual intervention.

Related Issue

Fixes #500

Dependant PRs

Type of Change

  • ✅ Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactoring (no functional changes)
  • 📄 Example update (no functional changes)
  • 📝 Documentation update
  • 🔍 Performance improvement
  • 🧪 Test update

How Has This Been Tested?

Screenshots

Checklist

  • I have read the CONTRIBUTING document
  • My code follows the project's coding standards
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works (if applicable)
  • Any dependent changes have been highlighted, merged or published

@colinmurphy
Automate release type detection in workflow
21c75d4 
Added a step to determine if the release is a pre-release or full release based on the version number. The release title and prerelease flag are now set dynamically, improving automation and reducing manual intervention.
@changeset-bot
Copy link

changeset-bot bot commented Nov 20, 2025

⚠️ No Changeset found

Latest commit: 21c75d4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@colinmurphy colinmurphy marked this pull request as ready for review November 20, 2025 14:32
@colinmurphy colinmurphy requested a review from a team as a code owner November 20, 2025 14:32
@colinmurphy colinmurphy added this pull request to the merge queue Nov 20, 2025
Merged via the queue into main with commit b95f669 Nov 20, 2025
2 checks passed
@colinmurphy colinmurphy deleted the chore-fix-500-release-tag-issue branch November 20, 2025 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ahuseyn ahuseyn ahuseyn approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

chore: Update pre-release workflow

3 participants

@colinmurphy @ahuseyn