Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Conversation

@amirh
Copy link
Contributor

@amirh amirh commented Nov 1, 2019

No description provided.

@amirh amirh force-pushed the publish_check_stable branch from 338017e to cbf8147 Compare November 1, 2019 17:52
Copy link
Contributor

@mklim mklim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@amirh amirh force-pushed the publish_check_stable branch from cbf8147 to 4d2f19a Compare November 1, 2019 18:13
@cyanglaz
Copy link
Contributor

@amirh Why did we decide not to run publish with master?

@mklim
Copy link
Contributor

mklim commented May 13, 2020

@cyanglaz at the time this PR was merged master had publish warnings that we were failing, if I remember correctly because of the new federated plugin format. Also if I remember correctly there wasn't a way to satisfy the warnings and also stay backwards compatible with stable. Since there's been a new stable roll relatively recently I don't think this still applies, but not 100% sure.

@cyanglaz
Copy link
Contributor

@mklim Thanks!I would like to confirm that and bring back the publish check on master. I guess you are right, I have a vague memory of this too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants