-
Notifications
You must be signed in to change notification settings - Fork 636
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
fix(gha): only bump halyard on master #1490
Merged
mergify
merged 1 commit into
spinnaker:master
from
dbyron-sf:only-bump-halyard-on-master
Aug 18, 2024
Merged
fix(gha): only bump halyard on master #1490
mergify
merged 1 commit into
spinnaker:master
from
dbyron-sf:only-bump-halyard-on-master
Aug 18, 2024
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
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50.
dbyron-sf
force-pushed
the
only-bump-halyard-on-master
branch
from
August 17, 2024 21:23
ff28693
to
1433816
Compare
@Mergifyio backport release-1.34.x release-1.35.x |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Aug 18, 2024
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50. (cherry picked from commit edc56d9)
mergify bot
pushed a commit
that referenced
this pull request
Aug 18, 2024
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50. (cherry picked from commit edc56d9)
mergify bot
added a commit
that referenced
this pull request
Aug 18, 2024
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50. (cherry picked from commit edc56d9) Co-authored-by: David Byron <[email protected]>
mergify bot
added a commit
that referenced
this pull request
Aug 18, 2024
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50. (cherry picked from commit edc56d9) Co-authored-by: David Byron <[email protected]>
christosarvanitis
pushed a commit
to armory-io/front50
that referenced
this pull request
Aug 22, 2024
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50.
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.
Since halyard uses a different versioning scheme, it doesn't make sense for halyard to consume non-master (e.g. release-1.34.x) versions of front50.
Similar to spinnaker/clouddriver#6268 + spinnaker/clouddriver#6271.