Skip to content
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
merged 1 commit into from
Aug 18, 2024

Conversation

dbyron-sf
Copy link
Contributor

@dbyron-sf dbyron-sf commented Aug 17, 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.

Similar to spinnaker/clouddriver#6268 + spinnaker/clouddriver#6271.

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 dbyron-sf added the ready to merge Approved and ready for merge label Aug 18, 2024
@mergify mergify bot added the auto merged label Aug 18, 2024
@mergify mergify bot merged commit edc56d9 into spinnaker:master Aug 18, 2024
4 checks passed
@dbyron-sf dbyron-sf deleted the only-bump-halyard-on-master branch August 18, 2024 02:01
@dbyron-sf
Copy link
Contributor Author

@Mergifyio backport release-1.34.x release-1.35.x

Copy link
Contributor

mergify bot commented Aug 18, 2024

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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants