Skip to content

configure trusted publishing for libc#2619

Open
marcoieni wants to merge 1 commit into
mainfrom
configure-trusted-publishing-for-libc
Open

configure trusted publishing for libc#2619
marcoieni wants to merge 1 commit into
mainfrom
configure-trusted-publishing-for-libc

Conversation

@marcoieni

@marcoieni marcoieni commented Jul 22, 2026

Copy link
Copy Markdown
Member

Related to rust-lang/libc#5317
When merging this, rust-lang-owner should remove individual access and undeclared teams

@marcoieni
marcoieni force-pushed the configure-trusted-publishing-for-libc branch 2 times, most recently from e11dc11 to 237abff Compare July 22, 2026 17:08
@marcoieni
marcoieni marked this pull request as ready for review July 22, 2026 17:11
@github-actions

github-actions Bot commented Jul 22, 2026

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 `ctest` to `true`
      Adding `team` owner `github:rust-lang:libs` to krate `ctest`
      Setting trusted publishing only option for krate `libc` to `true`
      Removing `team` owner `github:rust-lang:libc` from krate `libc`

[INFO rust_team::sync] synchronizing github
[INFO rust_team::sync] 💻 Repo Diffs:
📝 Editing repo 'rust-lang/libc':
Environments:
➕ Create: release
Branches: main, libc-0.2

Comment thread repos/rust-lang/libc.toml Outdated
Comment on lines +40 to +41
[environments.release]
branches = ["main"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We need libc-0.2 as well

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.

done, if you want to generalize in the future, you can have libc-* both in the ruleset and in the environment I think

@marcoieni
marcoieni force-pushed the configure-trusted-publishing-for-libc branch from 237abff to b1156d3 Compare July 22, 2026 17:21

@tgross35 tgross35 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks!

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.

2 participants