Closed deldrid1 closed 2 months ago
https://github.com/kdy1/trpc-openapi/blob/b61b76cd6dbbdb7285a1916833bd3c65e1895d72/package.json#L35
https://github.com/kdy1/trpc-openapi/blob/b61b76cd6dbbdb7285a1916833bd3c65e1895d72/package.json#L48-L49
Any reason to not pin the versions to @trpc/...: @next instead of a specific release candidate so that folks can stay up to date through the RC process?
@trpc/...: @next
Lost my brain for a bit this morning. I don't think this is actually possible...
https://github.com/kdy1/trpc-openapi/blob/b61b76cd6dbbdb7285a1916833bd3c65e1895d72/package.json#L35
https://github.com/kdy1/trpc-openapi/blob/b61b76cd6dbbdb7285a1916833bd3c65e1895d72/package.json#L48-L49
Any reason to not pin the versions to
@trpc/...: @next
instead of a specific release candidate so that folks can stay up to date through the RC process?