-
Notifications
You must be signed in to change notification settings - Fork 50
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!: reexport cargo-near-build
for configurable build if needed
#386
Conversation
@race-of-sloths include |
@dj8yfo 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 3! @akorchyn received 25 Sloth Points for reviewing and scoring this pull request. Another weekly streak completed, well done @dj8yfo! 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
|
cargo-near-build
for configurable build if neededcargo-near-build
for configurable build if needed
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 3
## 🤖 New release * `near-workspaces`: 0.14.1 -> 0.15.0 (✓ API compatible changes) <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.15.0](near-workspaces-v0.14.1...near-workspaces-v0.15.0) - 2024-11-18 ### Other - [**breaking**] updates near-* dependencies to 0.27 release ([#387](#387)) - [**breaking**] reexport `cargo-near-build` for configurable build if needed ([#386](#386)) - make cargo-near-build optional in manifest ([#383](#383)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/MarcoIeni/release-plz/).
PR addresses this TODO near/near-sdk-rs#1253 (comment) , which later
will behas been removed fromnear-sdk
code, for cases:static std::sync::OnceLock<T>/LazyLock<T, F>
creation like here https://github.com/dj8yfo/near-sdk-rs/blob/7be211e1b2991f6c5b4db78972784dac2f066e32/examples/fungible-token/tests/workspaces.rs#L47no-abi
here https://github.com/dj8yfo/abstract-dao/blob/fe9d16797bf582f0ea24380c1e4ad6bdb8c97283/tests/common.rs#L33PR avoids necessity to import
cargo-near-build
separately as a dependencyPR should best be published with a major release, to avoid weird breakage
0.14.1 -> 0.14.x