ci: use crates api to get owner list #31348
Conversation
yihau
force-pushed
the
specific-crate-token
branch
from
a26509f to
5046625
Compare
yihau
force-pushed
the
specific-crate-token
branch
2 times, most recently
from
c8f9a54 to
d12bf84
Compare
| result="$(cargo owner --list -q "$crate_name" --token "$CRATE_TOKEN" 2>&1)" | ||
| if [[ $result =~ ^error ]]; then | ||
| if [[ $result == *"Not Found"* ]]; then | ||
| response=$(curl -s https://crates.io/api/v1/crates/"$crate_name"/owners) |
There was a problem hiding this comment.
i think we'll be subject to lower api rate-limits without the token, so we need to keep an eye on that
|
automerge label removed due to a CI failure |
mergify
bot
removed
the
automerge
(hi, i'm becoming a github action/workflow pro recently) well, this is expected. pr can't access to secretes as indicated below when kicked by
|
|
yeah! thank you for the useful checking method! I think they changed something (like fix or publish new features) cuz our PR works fine with the same method/flow earlier. (like this one https://github.com/solana-labs/solana/actions/runs/4778963531/jobs/8495728916 ) and iirc when I implemented this feature, we could still get the secret correctly if we didn't modify the yml. (sounds risky today though) it just break on that day 🤔 |
Problem
seems that we can't get CRATE_TOKEN correctly in a PR.
Summary of Changes
just use curl to get crates owner list