mikeleppane
chamber
BlogDocsChangelog

Performance History

No performance history available yetOnce you have some commits, you will be able to see the performance history of your primary branch.

Latest Results

Fix: application crash reported due to illegal instruction. Most likely "target-cpu=native" flag causes it. (#18) Update dependencies and version to 0.5.4; refine rustflags for target configurations
main
3 months ago
Fix: application crash reported due to illegal instruction. Most likely "target-cpu=native" flag causes it. Update dependencies and version to 0.5.4; refine rustflags for target configurations
fix(I17)/application-crashes-config-file-missing
3 months ago
Update to v0.5.3: Add `.cargo/config.toml` with linting, compiler optimizations, and test-specific configurations; adjust workspace package metadata and profiles. (#15)
main
3 months ago
Update to v0.5.3: Add `.cargo/config.toml` with linting, compiler optimizations, and test-specific configurations; adjust workspace package metadata and profiles.
fix(profile)/update-profile-release
3 months ago
Chore(crates)/upload project to crates.io (#14) * Introduce `publish_all.py` to automate crate publishing and update workspace dependencies - Added `scripts/publish_all.py` for managing the crate publishing workflow, including dependency updates, publishing order, and restoration of Cargo.toml files. - Updated all crates with workspace-compatible metadata (`version`, `edition`, etc.) and keywords for improved categorization. - Added individual README files for each crate to enhance documentation and visibility on crates.io. - Standardized crate versions to `0.5.2` across the workspace. - Updated `.gitignore` to include Python virtual environment folders. * Update `chamber-vault` dependency to version `0.5.2` across workspace * Update `chamber-import-export` and `chamber-vault` dependencies to version `0.5.2` in `Cargo.toml` and `Cargo.lock` * Update `chamber-vault`, `chamber-password-gen`, and `chamber-import-export` dependencies to version `0.5.2` in `Cargo.toml` and `Cargo.lock` * Update `chamber-vault`, `chamber-password-gen`, and `chamber-import-export` dependencies to version `0.5.2` in `Cargo.toml` and `Cargo.lock` * Update `chamber-backup`, `chamber-cli`, `chamber-ui`, and `chamber-vault` dependencies to version `0.5.2` in `Cargo.toml` * Update `chamber-cli` dependency to version `0.2.0` in `Cargo.toml` * Set `time` dev-dependency to use workspace version in `Cargo.toml` * Update package name and set dependencies to version `0.5.2` in `Cargo.toml` * Fix typo in package name: `chamber--secret-manager-cli` to `chamber-secret-manager-cli` in `Cargo.toml`. * Update `chamber-cli` to `chamber-secret-manager-cli` and synchronize dependencies with version updates in `Cargo.toml` and `Cargo.lock`. * Rename package from `chamber` to `chamber-tui` and update dependencies in `Cargo.toml` and `Cargo.lock`. * Update `README.md` to reflect repository URL change and adjust installation instructions for `chamber-tui`. * Set all dependencies to use workspace versions in `Cargo.toml` and clean up redundant entries in `Cargo.lock`. Improve `publish_crate` logic in `publish_all.py`.
main
3 months ago
Set all dependencies to use workspace versions in `Cargo.toml` and clean up redundant entries in `Cargo.lock`. Improve `publish_crate` logic in `publish_all.py`.
chore(crates)/upload-project-to-crates.io
3 months ago
Implement auto-lock functionality across UI and core (#13) (#13) - Added `AutoLockConfig` and `ActivityTracker` modules to manage inactivity-based locking, with default configurations. - Introduced `AutoLockService` to provide a background service for triggering auto-lock based on user inactivity. - Updated TUI interface to display inactivity countdown, with visual alerts for imminent auto-lock. - Extended `App` struct with methods for managing auto-lock lifecycle and updating activity periodically. - Adjusted `run_app` to run async, enabling regular countdown updates and activity checks. - Removed redundant dependencies across crates; updated crate versions to `0.5.2`.
main
3 months ago
Implement auto-lock functionality across UI and core (#13) - Added `AutoLockConfig` and `ActivityTracker` modules to manage inactivity-based locking, with default configurations. - Introduced `AutoLockService` to provide a background service for triggering auto-lock based on user inactivity. - Updated TUI interface to display inactivity countdown, with visual alerts for imminent auto-lock. - Extended `App` struct with methods for managing auto-lock lifecycle and updating activity periodically. - Adjusted `run_app` to run async, enabling regular countdown updates and activity checks. - Removed redundant dependencies across crates; updated crate versions to `0.5.2`.
feat(security)/implement-auto-locking
3 months ago

Active Branches

No pull requests foundAs pull requests are created, their performance will appear here.
© 2025 CodSpeed Technology
Home Terms Privacy Docs