chore(dependencies): don't create an autobump PR for halyard on a kor… #948
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…k release branch since release branches in halyard don't align with release branches in kork. For example, a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions.
link108
approved these changes
Apr 2, 2022
|
@Mergifyio backport release-1.28.x release-1.29.x |
mergify bot
pushed a commit
that referenced
this pull request
Oct 22, 2022
…k release branch (#948) since release branches in halyard don't align with release branches in kork. For example, a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 53938f5)
mergify bot
pushed a commit
that referenced
this pull request
Oct 22, 2022
…k release branch (#948) since release branches in halyard don't align with release branches in kork. For example, a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 53938f5)
✅ Backports have been created
|
mergify bot
added a commit
that referenced
this pull request
Oct 22, 2022
…k release branch (#948) (#988) since release branches in halyard don't align with release branches in kork. For example, a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 53938f5) Co-authored-by: David Byron <[email protected]>
mergify bot
added a commit
that referenced
this pull request
Oct 22, 2022
…k release branch (#948) (#989) since release branches in halyard don't align with release branches in kork. For example, a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 53938f5) Co-authored-by: David Byron <[email protected]>
|
@Mergifyio backport release-1.30.x |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Apr 5, 2023
…k release branch (#948) since release branches in halyard don't align with release branches in kork. For example, a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 53938f5)
|
When https://github.com/spinnaker/spinnaker/projects/20#card-85655999 is complete, we won't need to keep backporting this each time we make new release branches. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…k release branch
since release branches in halyard don't align with release branches in kork. For example,
a release-1.27.x branch exists in both kork and halyard. In kork release-1.27.x aligns
with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker
versions.