-
Notifications
You must be signed in to change notification settings - Fork 30
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
Investigation/Todo: Release-Pipeline umsetzen/optimieren #6566
Comments
3 tasks
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
Closed
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
…p-publish * origin/6566-bump-publish: (#6566) 1.7.26-alpha.0
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
…p-publish * origin/6566-bump-publish: (#6566) chore: release 1.7.26-alpha.1
sdvg
added a commit
that referenced
this issue
Jul 1, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Aktuell wird die Versionsnummer manuell gesetzt und anschließend auf den Release-Branches die Public-Pipeline ausgeführt.
release
-Branch)release
-Branch und commited die Versionsnummer nach dem Durchlauf zurück.The text was updated successfully, but these errors were encountered: