Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update the package name and version #7

Merged
merged 1 commit into from
Jan 10, 2025
Merged

Conversation

nazarhussain
Copy link

Motivation

Update the package name and version for standalone release as @chainsafe/benchmark.

Description

  • Update the package version
  • Update the package name
  • Update docs

Steps to test or reproduce

  • Run all tests

Copy link
Member

@matthewkeil matthewkeil left a comment

Choose a reason for hiding this comment

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

Couple small changes and the question about leaving dapplion's name in the comments to pay homage to his work on this before we forked it

README.md Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
src/utils/gaContext.ts Outdated Show resolved Hide resolved
Copy link
Member

@matthewkeil matthewkeil left a comment

Choose a reason for hiding this comment

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

LGTM 🎸

Base automatically changed from nh/embeded-runner to main December 12, 2024 16:03
Copy link

github-actions bot commented Jan 10, 2025

Performance Report

✔️ no performance regression detected

Full benchmark results
Benchmark suite Current: cf5d852 Previous: null Ratio
sum array with raw for loop 933.66 us/op
sum array with reduce 9.4687 ms/op
sum array with reduce beforeEach 9.6115 ms/op
sum array with reduce before beforeEach 9.6803 ms/op
sum array with reduce high threshold 9.8462 ms/op
sum array with reduce no threshold 9.8656 ms/op

by benchmarkbot/action

"repository": "[email protected]:dapplion/benchmark.git",
"author": "dapplion <[email protected]>",
"name": "@chainsafe/benchmark",
"version": "1.1.0.rc-0",
Copy link
Author

Choose a reason for hiding this comment

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

The only key factor is the version number. As we forked the repo from the version 1.0.0 originally, But it's a newer package completely, should we use 1.1.0 or start from zero versioning 0.1.0?

Copy link
Member

@nflaig nflaig Jan 10, 2025

Choose a reason for hiding this comment

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

it's stable enough I would go with 1.1.0 or even 1.0.0 since it's a new package... 0.x.x is really the lazy way to do versioning and is pretty bad for consumers

Copy link
Author

Choose a reason for hiding this comment

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

There are lot of thoughts behind zero versioning scheme. https://0ver.org/

@nazarhussain nazarhussain merged commit 69d783d into main Jan 10, 2025
13 checks passed
@nazarhussain nazarhussain deleted the nh/package-version branch January 10, 2025 09:56
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.

3 participants