-
Notifications
You must be signed in to change notification settings - Fork 16
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
Tracking cargo near new
usage
#192
Conversation
cargo near new
usagecargo near new
usage
@garikbesson Thank you for your contribution! Your pull request is now a part of the Race of Sloths! Current status: executed
Your contribution is much appreciated with a final score of 5! Another weekly streak completed, well done @garikbesson! To keep your weekly streak and get another bonus make pull request next week! Looking forward to see you in race-of-sloths What is the Race of SlothsRace of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow For contributors:
For maintainers:
Feel free to check our website for additional details! Bot commands
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@race-of-sloths score 5
## 🤖 New release * `cargo-near`: 0.8.2 -> 0.9.0 * `cargo-near-build`: 0.1.0 -> 0.1.1 <details><summary><i><b>Changelog</b></i></summary><p> ## `cargo-near` <blockquote> ## [0.9.0](cargo-near-v0.8.2...cargo-near-v0.9.0) - 2024-09-12 ### Added - Fixed GitHub CI staging workflow generated by `cargo near new` command to work correctly with docker case ([#193](#193)) - Extracted cargo-near-build into a standalone crate to be able to use it in near-workspaces and other places without the rest of the heavy dependencies of cargo-near ([#198](#198)) - Added tracking of `cargo near new` usage to collect statistics of the command usage ([#192](#192)) ### Fixed - Addressed warnings in `cargo build -p cargo-near-build` cmd in releaze-plz flow ([#212](#212)) ### Other - Updated near-* dependencies to 0.26 release ([#220](#220)) - Use "tracing" for logging and loading indicators ([#216](#216)) - update docker image and sdk version in `cargo near new` template ([#218](#218)) - [**breaking**] updates near-* packages to 0.25 version. Updates near-sdk to 5.4 ([#215](#215)) </blockquote> ## `cargo-near-build` <blockquote> ## [0.1.1](cargo-near-build-v0.1.0...cargo-near-build-v0.1.1) - 2024-09-12 ### Added - Fixed GitHub CI staging workflow generated by `cargo near new` command to work correctly with docker case ([#193](#193)) ### Other - Use "tracing" for logging and loading indicators ([#216](#216)) - fix clippy ([#219](#219)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/MarcoIeni/release-plz/).
The issue: #185
How tracking events looks like:
UPDATE: sending field
pkg_version
instead ofcli_version