{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 ▲ chillily 的问题《Inconsistent NuGet package and assembly versions》','https://www.manongdao.com/q-1125036.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
The NuGet package System.IdentityModel.Tokens.Jwt , version 4.0.2.206221351, found here contains an assembly System.IdentityModel.Tokens.Jwt.dll that has version 4.0.20622.1351, different from version of the NuGet package.
Why this is not a huge problem?
NuGet package version numbers are not related to assembly version numbers. They can be different, and must be different from now on, as the package number follow Semantic Versioning.