chore(dependencies): don't create an autobump PR for halyard on a fro… #1115
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
…nt50 release branch since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 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 |
mergify bot
pushed a commit
that referenced
this pull request
Apr 9, 2022
…nt50 release branch (#1115) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17)
✅ Backports have been created
|
|
@Mergifyio backport release-1.29.x |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Sep 26, 2022
…nt50 release branch (#1115) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17)
mergify bot
added a commit
that referenced
this pull request
Sep 26, 2022
…nt50 release branch (#1115) (#1165) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17) Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com>
|
@Mergifyio backport release-1.30.x |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Apr 5, 2023
…nt50 release branch (#1115) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17)
mergify bot
added a commit
that referenced
this pull request
Apr 5, 2023
…nt50 release branch (#1115) (#1247) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17) Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com>
yugaa22
pushed a commit
to OpsMx/front50-oes
that referenced
this pull request
Jun 26, 2023
…nt50 release branch (spinnaker#1115) (spinnaker#1247) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17) Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com>
yugaa22
pushed a commit
to OpsMx/front50-oes
that referenced
this pull request
Jun 26, 2023
…nt50 release branch (spinnaker#1115) (spinnaker#1247) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17) Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com>
aman-agrawal
pushed a commit
to aman-agrawal/front50
that referenced
this pull request
Jun 28, 2024
…nt50 release branch (spinnaker#1115) (spinnaker#1247) since release branches in halyard don't align with release branches in front50. For example, a release-1.27.x branch exists in both front50 and halyard. In front50 release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are independent from spinnaker versions. (cherry picked from commit 7fbae17) Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com>
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.
…nt50 release branch
since release branches in halyard don't align with release branches in front50. For
example, a release-1.27.x branch exists in both front50 and halyard. In front50
release-1.27.x aligns with spinnaker version 1.27.x, but halyard version numbers are
independent from spinnaker versions.