fix: update syn crate to match near-sdk crate and to enable parsing of #[unsafe(no_mangle)]#171
Merged
Conversation
r-near
approved these changes
Mar 26, 2026
This was referenced Mar 27, 2026
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes
near-plugins-derivemacro code generation to work withnear-sdk v5.25.0.near-sdk v5.25.0adopted Rust edition 2024, which requires#[unsafe(no_mangle)]instead of#[no_mangle]. Thenear_bindgenproc macro now emits#[unsafe(no_mangle)]on generated wrapper functions.near-plugins-derivedepended onsyn 1.x, which cannot parse this attribute syntax, causing all#[pause],#[access_control_any], and#[derive(Pausable)]usages to fail witherror: expected path.Related links