update the major version number

[haifengkao]

I think you should update the major version number when you adopts the new major version of swift-syntax.
In order to avoid error messages like below

error: Dependencies could not be resolved because root depends on 'macro-codable-kit' 0.3.0..<1.0.0 and 'swiftrexmacros' depends on 'swift-syntax' 509.0.0..<510.0.0.
'macro-codable-kit' >= 0.3.0 practically depends on 'swift-syntax' {509.0.0, 510.0.0..<511.0.0, 600.0.1..<601.0.0}.
'macro-codable-kit' >= 0.3.0 practically depends on 'swift-macro-toolkit' 0.3.0..<1.0.0 because 'macro-codable-kit' 0.3.0 depends on 'swift-macro-toolkit' 0.3.0..<1.0.0 and no versions of 'macro-codable-kit' match the requirement 0.3.1..<1.0.0.
'swift-macro-toolkit' >= 0.3.0 practically depends on 'swift-syntax' {509.0.0, 510.0.0..<511.0.0, 600.0.1..<601.0.0} because 'swift-macro-toolkit' 0.5.0 depends on 'swift-syntax' 510.0.0..<511.0.0 and 'swift-macro-toolkit' 0.6.0 depends on 'swift-syntax' 600.0.1..<601.0.0.
'swift-macro-toolkit' {0.3.0..<0.5.0, 0.5.1..<0.6.0, 0.6.1..<1.0.0} practically depends on 'swift-syntax' {509.0.0, 510.0.0..<511.0.0} because 'swift-macro-toolkit' 0.3.1 depends on 'swift-syntax' 509.0.0 and 'swift-macro-toolkit' 0.4.0 depends on 'swift-syntax' 510.0.0..<511.0.0.
'swift-macro-toolkit' {0.3.0..<0.3.1, 0.3.2..<0.4.0, 0.4.1..<0.5.0, 0.5.1..<0.6.0, 0.6.1..<1.0.0} practically depends on 'swift-syntax' 509.0.0 because 'swift-macro-toolkit' 0.3.0 depends on 'swift-syntax' 509.0.0.
'swift-macro-toolkit' {0.3.0, 0.3.2..<0.4.0, 0.4.1..<0.5.0, 0.5.1..<0.6.0, 0.6.1..<1.0.0} practically depends on 'swift-syntax' 509.0.0 because no versions of 'swift-macro-toolkit' match the requirement {0.3.2..<0.4.0, 0.4.1..<0.5.0, 0.5.1..<0.6.0, 0.6.1..<1.0.0} and 'swift-macro-toolkit' 0.3.0 depends on 'swift-syntax' 509.0.0.

[stackotter]

Thanks for bringing this to my attention, I didn't realise that SwiftPM treated 0.x.0 and 0.(x+1).0 as compatible (because before 1.0.0, people generally bump the minor version on breaking changes instead of the major version afaik).

But yeah, SwiftMacroToolkit seems to have ended up with quite a few users now so it probably is time for a proper release. I'll try getting around to cleaning things up for a proper release then releasing 1.0.0.