Skip to content

Configure trusted publishing for futures-rs#2594

Open
Kobzol wants to merge 1 commit into
rust-lang:mainfrom
Kobzol:futures-rs-trusted-publishing
Open

Configure trusted publishing for futures-rs#2594
Kobzol wants to merge 1 commit into
rust-lang:mainfrom
Kobzol:futures-rs-trusted-publishing

Conversation

@Kobzol

@Kobzol Kobzol commented Jul 18, 2026

Copy link
Copy Markdown
Member

@github-actions

Copy link
Copy Markdown
Dry-run check results

[WARN  rust_team::sync] sync-team is running in dry mode, no changes will be applied.
[INFO  rust_team::sync] synchronizing crates-io
[INFO  rust_team::sync] 💻 Trusted Publishing Crate Diffs:
      Setting trusted publishing only option for krate `futures` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures`
      Setting trusted publishing only option for krate `futures-channel` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-channel`
      Setting trusted publishing only option for krate `futures-core` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-core`
      Setting trusted publishing only option for krate `futures-executor` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-executor`
      Setting trusted publishing only option for krate `futures-io` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-io`
      Setting trusted publishing only option for krate `futures-macro` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-macro`
      Setting trusted publishing only option for krate `futures-sink` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-sink`
      Setting trusted publishing only option for krate `futures-task` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-task`
      Setting trusted publishing only option for krate `futures-test` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-test`
      Setting trusted publishing only option for krate `futures-util` to `true`
      Adding `team` owner `github:rust-lang:wg-async` to krate `futures-util`

[INFO rust_team::sync] synchronizing github
[INFO rust_team::sync] 💻 Repo Diffs:
📝 Editing repo 'rust-lang/futures-rs':
Environments:
➕ Create: publish
Branches: main

@taiki-e taiki-e left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks!

]
publish-workflow = "publish.yml"
publish-environment = "publish"
teams = ["wg-async"]

@taiki-e taiki-e Jul 18, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this an approver? Since cramertj stopped being involved (5-6 years ago?) I'm the only current member of wg-async who has been involved in maintaining futures-rs, it seems odd that all wg members would have permission over releases.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This specifies which team will own the crate on crates.io. But in practice with trusted publishing turned on, the only thing that this is useful for is yanking.

By the way, it would be great if the current active roster of wg-async was updated to match today's state!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Technically these people have access to turn off trusted publishing and manually publish, but that would be a loud-ish action. Long-term I personally would like us to remove all human access to crates.io' (probably proxying yanks via some github/zulip bot) and/or have stronger yank-only enforcemeent.

[environments.github-pages]

[environments.publish]
branches = ["main"]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
branches = ["main"]
branches = ["0.3"]

At this time, we don't create any release from main.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants