Update CodSpeed workflow to v4 with OIDC authentication#11
Merged
Conversation
Contributor
Author
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
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.
This PR updates the existing CodSpeed integration to use the latest best practices.
Changes
CodSpeed workflow (
.github/workflows/codspeed.yml)secrets.CODSPEED_TOKENdependency and addedid-token: writepermission. OIDC is the recommended authentication method for CodSpeed, removing the need to manage repository secrets.mode: simulation-- uses CodSpeed's CPU simulation instrument for consistent, hardware-agnostic measurements that are not affected by CI runner load.workflow_dispatchcomment explaining its purpose for CodSpeed backtesting.README
Existing setup retained
The repository already had a well-configured benchmark setup:
@codspeed/vitest-pluginv5.3.0 integrated invitest.bench.config.tsbench/operations.bench.tsandbench/difference.bench.tscovering tree operations, search, chop, merge, set operations, and more.No changes were needed to the benchmark files or plugin configuration.
Next steps
workflow_dispatchto generate initial baseline data.Need help on this PR? Tag
@codesmithwith what you need.