We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@backstage/plugin-git-release-manager
Can't promote Release Candidate with semantic versioning when i have created a second version with the plugin.
Release Candidate is promoted, branch with correct name is created and a release is created
The problem is seen in the picture.
One can't set the pre-release as latest release when multiple releases exist. This code has a logic flaw:
community-plugins/workspaces/git-release-manager/plugins/git-release-manager/src/features/PromoteRc/PromoteRc.tsx
Line 39 in dfe7569
The promoteRC should fetch all RC releases and user should be able to chose which RC should be promoted.
No, but I'm happy to collaborate on a PR with someone else
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Plugin Name
@backstage/plugin-git-release-manager
📜 Description
Can't promote Release Candidate with semantic versioning when i have created a second version with the plugin.
👍 Expected behavior
Release Candidate is promoted, branch with correct name is created and a release is created
👎 Actual Behavior with Screenshots
The problem is seen in the picture.
👟 Reproduction steps
📃 Provide the context for the Bug.
One can't set the pre-release as latest release when multiple releases exist. This code has a logic flaw:
community-plugins/workspaces/git-release-manager/plugins/git-release-manager/src/features/PromoteRc/PromoteRc.tsx
Line 39 in dfe7569
The promoteRC should fetch all RC releases and user should be able to chose which RC should be promoted.
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else
The text was updated successfully, but these errors were encountered: