fix(ci): remove environment from publish workflow#23
Merged
jasonz-dfinity merged 1 commit intomainfrom Feb 26, 2026
Merged
Conversation
The crates.io trusted publisher config for this crate does not specify an environment, so the workflow must not specify one either. This mismatch caused the OIDC token exchange to fail with a 400 error.
jasonz-dfinity
force-pushed
the
fix/publish-remove-environment
branch
from
3f7395f to
c2a9465
Compare
0xFFrancesco
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
environment: releasefrom the publish workflow to match the crates.io trusted publisher configuration, which does not specify an environmentNo Trusted Publishing config found for repository dfinity/metrics-encoderenvironment: releasedoesn't provide any benefit since the repo's write access is protected alreadyAfter merging
Re-run the failed v1.1.2 release workflow, or delete and re-create the release to re-trigger publishing.