Skip to content
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.

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

Defining Pre-Release Versions: Beta, Alpha, RC, and Version Bumping (--bump) #692

Closed
1 task done
bukowa opened this issue Jun 11, 2024 · 1 comment · Fixed by #695
Closed
1 task done

Defining Pre-Release Versions: Beta, Alpha, RC, and Version Bumping (--bump) #692

bukowa opened this issue Jun 11, 2024 · 1 comment · Fixed by #695
Assignees
Labels
feature/request New feature or request

Comments

@bukowa
Copy link
Contributor

bukowa commented Jun 11, 2024

Is there an existing issue or pull request for this?

  • I have searched the existing issues and pull requests

Feature description

Releasing beta, RC (release candidate), or alpha versions is a common standard practice, especially when we want to test the entire build system. Sometimes these releases help ensure that the build scripts execute correctly and provide users with a preview version (e.g., a beta version), which is essentially complete but still in testing.

Sometimes, releasing a release candidate is necessary to verify the functionality of build scripts. It would be beneficial to standardize this process, allowing for the automatic generation of changelogs for these versions and their subsequent integration into the main release. Combining this with version bumping, while maintaining logical and configurable control, would be highly advantageous.

Desired solution

Simple idea for bumping:

git-cliff --bump-beta
git-cliff --bump-alpha
git-cliff --bump-rc

No simple idea for changelogs but see :

This doesn't seem so straightforward as everyone has their standards and this somehow should be customizable?

Alternatives considered

Manual bumping.

Additional context

Given the variety of standards used by different projects, it would be beneficial to provide customizable configuration keys for tags like rc, alpha, and beta. This would allow users to tailor the versioning system to their specific requirements.

bump_beta = ...<format>
bump_alpha = ...<format>

OR

[rc]
header = "Release Candidate Changes"
label = "RC"
# Configuration for alpha versions
[alpha]
header = "Alpha Version Changes"
label = "Alpha"
# Configuration for beta versions
[beta]
header = "Beta Version Changes"
label = "Beta"
@bukowa bukowa added the feature/request New feature or request label Jun 11, 2024
@bukowa
Copy link
Contributor Author

bukowa commented Jun 12, 2024

It's not so easy for ex release-please from google issue regarding this: googleapis/release-please#2051

I just tried to release tauri app but automatic build fails because wix does not support anything other than numbers in version tauri-apps/tauri#5286 (comment)

@bukowa bukowa closed this as not planned Won't fix, can't repro, duplicate, stale Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants