CodSpeedHQ/codspeed - CodSpeed

codspeed

Blog Docs Changelog

Performance History

Latest Results

chore(deps): bump taiki-e/install-action from 2.79.4 to 2.79.9 Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.79.4 to 2.79.9. - [Release notes](https://github.com/taiki-e/install-action/releases) - [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/install-action/compare/e0eafa9a0d485c37f97c0f7beb930a58a2facbac...8f531eaecd1898bc3da7d104ad91bee98d1b97bd) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.79.9 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot/github_actions/taiki-e/install-action-2.79.9

10 hours ago

feat: add profile-based auth configuration (#366) * chore: auto-init submodules on worktree creation Add a pre-commit `post-checkout` stage hook that detects `git worktree add` (signalled by an all-zero previous HEAD) and initializes submodules + reinstalls pre-commit hooks in the new worktree. The config opts both stages into `default_install_hook_types` so a plain `prek install` wires up everything. Co-Authored-By: Claude <noreply@anthropic.com> * feat(cli): add profile system with versioned config Introduce named profiles in the CodSpeed CLI config. Each profile carries its own auth token plus optional api-url/upload-url overrides. Profile selection at runtime follows: `--profile` / `CODSPEED_PROFILE` env var, then a per-shell-session selection registered by `codspeed profile use` (parent-PID keyed file under `$XDG_RUNTIME_DIR/codspeed_profile`, mirroring how `codspeed use <mode>` works), then the built-in `default` profile. There is no globally persisted default profile. The on-disk config gains a `version: 1` schema field. A private `RawConfig` deserialisation type and a `migrate` function are the only place legacy YAML shapes are mentioned; when migration is needed the canonical form is rewritten to disk immediately so the rest of the app only ever sees the clean shape. Today this folds the legacy top-level `auth.token` into `profiles.default`. `CodSpeedConfig` is split: a private `PersistedConfig` is the on-disk shape (version + profiles), and `CodSpeedConfig` wraps it with the runtime-resolved auth/URLs/selected_profile. `persist` writes only the persisted half, so runtime overrides (e.g. `CODSPEED_OAUTH_TOKEN`) can never leak to disk. The parent-PID shell-session machinery used by `codspeed use <mode>` is extracted into a generic `shell_session_store` module so profile and runner-mode share the same implementation. `src/runner_mode/` is flattened into `src/runner_mode.rs` now that the sub-file is gone. Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>

main

12 hours ago

feat(cli): add profile system with versioned config Introduce named profiles in the CodSpeed CLI config. Each profile carries its own auth token plus optional api-url/upload-url overrides. Profile selection at runtime follows: `--profile` / `CODSPEED_PROFILE` env var, then a per-shell-session selection registered by `codspeed profile use` (parent-PID keyed file under `$XDG_RUNTIME_DIR/codspeed_profile`, mirroring how `codspeed use <mode>` works), then the built-in `default` profile. There is no globally persisted default profile. The on-disk config gains a `version: 1` schema field. A private `RawConfig` deserialisation type and a `migrate` function are the only place legacy YAML shapes are mentioned; when migration is needed the canonical form is rewritten to disk immediately so the rest of the app only ever sees the clean shape. Today this folds the legacy top-level `auth.token` into `profiles.default`. `CodSpeedConfig` is split: a private `PersistedConfig` is the on-disk shape (version + profiles), and `CodSpeedConfig` wraps it with the runtime-resolved auth/URLs/selected_profile. `persist` writes only the persisted half, so runtime overrides (e.g. `CODSPEED_OAUTH_TOKEN`) can never leak to disk. The parent-PID shell-session machinery used by `codspeed use <mode>` is extracted into a generic `shell_session_store` module so profile and runner-mode share the same implementation. `src/runner_mode/` is flattened into `src/runner_mode.rs` now that the sub-file is gone. Co-Authored-By: Claude <noreply@anthropic.com>

profiles-auth-environments

13 hours ago

feat(cli): add profile system with versioned config Introduce named profiles in the CodSpeed CLI config. Each profile carries its own auth token plus optional api-url/upload-url overrides. Profile selection at runtime follows: `--profile` / `CODSPEED_PROFILE` env var, then a per-shell-session selection registered by `codspeed profile use` (parent-PID keyed file under `$XDG_RUNTIME_DIR/codspeed_profile`, mirroring how `codspeed use <mode>` works), then the built-in `default` profile. There is no globally persisted default profile. The on-disk config gains a `version: 1` schema field. A private `RawConfig` deserialisation type and a `migrate` function are the only place legacy YAML shapes are mentioned; when migration is needed the canonical form is rewritten to disk immediately so the rest of the app only ever sees the clean shape. Today this folds the legacy top-level `auth.token` into `profiles.default`. `CodSpeedConfig` is split: a private `PersistedConfig` is the on-disk shape (version + profiles), and `CodSpeedConfig` wraps it with the runtime-resolved auth/URLs/selected_profile. `persist` writes only the persisted half, so runtime overrides (e.g. `CODSPEED_OAUTH_TOKEN`) can never leak to disk. The parent-PID shell-session machinery used by `codspeed use <mode>` is extracted into a generic `shell_session_store` module so profile and runner-mode share the same implementation. `src/runner_mode/` is flattened into `src/runner_mode.rs` now that the sub-file is gone. Co-Authored-By: Claude <noreply@anthropic.com>

profiles-auth-environments

13 hours ago

feat(cli): add profile system with versioned config Introduce named profiles in the CodSpeed CLI config. Each profile carries its own auth token plus optional api-url/upload-url overrides. Profile selection at runtime follows: `--profile` / `CODSPEED_PROFILE` env var, then a per-shell-session selection registered by `codspeed profile use` (parent-PID keyed file under `$XDG_RUNTIME_DIR/codspeed_profile`, mirroring how `codspeed use <mode>` works), then the built-in `default` profile. There is no globally persisted default profile. The on-disk config gains a `version: 1` schema field. A private `RawConfig` deserialisation type and a `migrate` function are the only place legacy YAML shapes are mentioned; when migration is needed the canonical form is rewritten to disk immediately so the rest of the app only ever sees the clean shape. Today this folds the legacy top-level `auth.token` into `profiles.default`. `CodSpeedConfig` is split: a private `PersistedConfig` is the on-disk shape (version + profiles), and `CodSpeedConfig` wraps it with the runtime-resolved auth/URLs/selected_profile. `persist` writes only the persisted half, so runtime overrides (e.g. `CODSPEED_OAUTH_TOKEN`) can never leak to disk. The parent-PID shell-session machinery used by `codspeed use <mode>` is extracted into a generic `shell_session_store` module so profile and runner-mode share the same implementation. `src/runner_mode/` is flattened into `src/runner_mode.rs` now that the sub-file is gone. Co-Authored-By: Claude <noreply@anthropic.com>

profiles-auth-environments

13 hours ago

feat(cli): add profile system with versioned config Introduce named profiles in the CodSpeed CLI config. Each profile carries its own auth token plus optional api-url/upload-url overrides. Profile selection at runtime follows: `--profile` / `CODSPEED_PROFILE` env var, then a per-shell-session selection registered by `codspeed profile use` (parent-PID keyed file under `$XDG_RUNTIME_DIR/codspeed_profile`, mirroring how `codspeed use <mode>` works), then the built-in `default` profile. There is no globally persisted default profile. The on-disk config gains a `version: 1` schema field. A private `RawConfig` deserialisation type and a `migrate` function are the only place legacy YAML shapes are mentioned; when migration is needed the canonical form is rewritten to disk immediately so the rest of the app only ever sees the clean shape. Today this folds the legacy top-level `auth.token` into `profiles.default`. `CodSpeedConfig` is split: a private `PersistedConfig` is the on-disk shape (version + profiles), and `CodSpeedConfig` wraps it with the runtime-resolved auth/URLs/selected_profile. `persist` writes only the persisted half, so runtime overrides (e.g. `CODSPEED_OAUTH_TOKEN`) can never leak to disk. The parent-PID shell-session machinery used by `codspeed use <mode>` is extracted into a generic `shell_session_store` module so profile and runner-mode share the same implementation. `src/runner_mode/` is flattened into `src/runner_mode.rs` now that the sub-file is gone. Co-Authored-By: Claude <noreply@anthropic.com>

profiles-auth-environments

14 hours ago

fix(skills): misleading DCE advice in setup-harness (#350) `benchmark.pedantic` is not a dead-code-elimination tool; it controls the measurement loop. CPython doesn't perform the kind of DCE that `black_box` guards against in compiled languages, so pure-Python benchmarks don't need an equivalent. List the actual primitives for the languages that do (C++: DoNotOptimize, JMH: Blackhole.consume).

main

14 hours ago

feat: bump instrument-hooks to not use stubs on macos (#373)

main

14 hours ago

Latest Branches

0%

chore(deps): bump taiki-e/install-action from 2.79.4 to 2.79.9#374

10 hours ago

5b68fea

dependabot/github_actions/taiki-e/install-action-2.79.9

0%

Add profile-based auth configuration#366

2 days ago

32a8425

profiles-auth-environments

0%

fix(skills): misleading DCE advice in setup-harness#350

11 days ago

8bf3d7d

fix/skill-pedantic-not-for-dce

© 2026 CodSpeed Technology

Home Terms Privacy Docs