How are backport fixes made into releases?
Answered
Saltwater Crocodile posted this in #help-forum
Saltwater CrocodileOP
My company is experiencing a [problem with our Datadog instrumentation](https://github.com/DataDog/dd-trace-js/issues/4243#issuecomment-2378995839). A fix has been made to Next.js but that fix hasn't made it into a stable release yet. I would like to cut a new release of 14.2.x that includes [this version bump to @vercel/nft](https://github.com/vercel/next.js/pull/65854).
Is cutting a new release something I can start or facilitate? Or do one of the primary maintainers need to start this process?
Is cutting a new release something I can start or facilitate? Or do one of the primary maintainers need to start this process?
Answered by joulev
One of the maintainers have to initiate. Only approved persons can make a release.
You/your company can fork nextjs, manually apply the code change there and release it yourself. Or use patch-package.
You/your company can fork nextjs, manually apply the code change there and release it yourself. Or use patch-package.
4 Replies
One of the maintainers have to initiate. Only approved persons can make a release.
You/your company can fork nextjs, manually apply the code change there and release it yourself. Or use patch-package.
You/your company can fork nextjs, manually apply the code change there and release it yourself. Or use patch-package.
Answer
Saltwater CrocodileOP
Thank you. We are considering doing the fork methodology you've suggested until a stable release is available. In the meantime, how does one get in contact with a maintainer to request a backport fix?
Assuming you don’t have personal contact with any of them, a github issue is your best bet, though the success rate is low.
Saltwater CrocodileOP
Appreciate you taking the time @joulev . I will open an issue and see where that lands.