The automated release is failing 🚨

[parseplatformorg]

🚨 The automated release from the release-7.x.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release-7.x.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 7.4.1 on branch release-7.x.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=7.4.0 <7.4.0 can be published from branch release-7.x.x.

The following commits are responsible for the invalid release:

• refactor: Upgrade @graphql-tools/merge from 9.0.15 to 9.0.17 (refactor: Upgrade @graphql-tools/merge from 9.0.15 to 9.0.17 #9589) (6cf2876)
• refactor: Upgrade @graphql-tools/merge from 9.0.14 to 9.0.15 (refactor: Upgrade @graphql-tools/merge from 9.0.14 to 9.0.15 #9544) (74dfc4e)
• refactor: Upgrade mime from 4.0.4 to 4.0.6 (refactor: Upgrade mime from 4.0.4 to 4.0.6 #9546) (ae16aba)
• ci: MongoDB 4, 5 CI jobs fail for LTS branch (ci: MongoDB 4, 5 CI jobs fail for LTS branch  #9536) (0fb0c07)
• fix: Push adapter not loading on some versions of Node 22 (fix: Push adapter not loading on some versions of Node 22 #9525) (5447c22)
• ci: Update auto release (ci: Update auto release #9520) (4ac8aef)
• ci: Udpate auto-release LTS branch (ci: Udpate auto-release LTS branch #9519) (82ab3f9)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release-7.x.x with git revert or git reset.

A valid branch could be release.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[parse-github-assistant]

The label semantic-release cannot be used here.

[parse-github-assistant]

Thanks for opening this issue!

[parseplatformorg]

🚨 The automated release from the release-7.x.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release-7.x.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 7.4.1 on branch release-7.x.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=7.4.0 <7.4.0 can be published from branch release-7.x.x.

The following commits are responsible for the invalid release:

• fix: Security upgrade node from 20.17.0-alpine3.20 to 20.18.2-alpine3.20 (fix: Security upgrade node from 20.17.0-alpine3.20 to 20.18.2-alpine3.20 #9597) (6114cd9)
• refactor: Upgrade @graphql-tools/merge from 9.0.15 to 9.0.17 (refactor: Upgrade @graphql-tools/merge from 9.0.15 to 9.0.17 #9589) (6cf2876)
• refactor: Upgrade @graphql-tools/merge from 9.0.14 to 9.0.15 (refactor: Upgrade @graphql-tools/merge from 9.0.14 to 9.0.15 #9544) (74dfc4e)
• refactor: Upgrade mime from 4.0.4 to 4.0.6 (refactor: Upgrade mime from 4.0.4 to 4.0.6 #9546) (ae16aba)
• ci: MongoDB 4, 5 CI jobs fail for LTS branch (ci: MongoDB 4, 5 CI jobs fail for LTS branch  #9536) (0fb0c07)
• fix: Push adapter not loading on some versions of Node 22 (fix: Push adapter not loading on some versions of Node 22 #9525) (5447c22)
• ci: Update auto release (ci: Update auto release #9520) (4ac8aef)
• ci: Udpate auto-release LTS branch (ci: Udpate auto-release LTS branch #9519) (82ab3f9)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release-7.x.x with git revert or git reset.

A valid branch could be release.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[parseplatformorg]

🚨 The automated release from the release-7.x.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release-7.x.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 7.5.0 on branch release-7.x.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=7.4.0 <7.4.0 can be published from branch release-7.x.x.

The following commits are responsible for the invalid release:

• feat: Add support for MongoDB databaseOptions keys minPoolSize, connectTimeoutMS, socketTimeoutMS, autoSelectFamily, autoSelectFamilyAttemptTimeout (feat: Add support for MongoDB databaseOptions keys minPoolSize, connectTimeoutMS, socketTimeoutMS, autoSelectFamily, autoSelectFamilyAttemptTimeout #9577) (20f2071)
• fix: Security upgrade node from 20.17.0-alpine3.20 to 20.18.2-alpine3.20 (fix: Security upgrade node from 20.17.0-alpine3.20 to 20.18.2-alpine3.20 #9597) (6114cd9)
• refactor: Upgrade @graphql-tools/merge from 9.0.15 to 9.0.17 (refactor: Upgrade @graphql-tools/merge from 9.0.15 to 9.0.17 #9589) (6cf2876)
• refactor: Upgrade @graphql-tools/merge from 9.0.14 to 9.0.15 (refactor: Upgrade @graphql-tools/merge from 9.0.14 to 9.0.15 #9544) (74dfc4e)
• refactor: Upgrade mime from 4.0.4 to 4.0.6 (refactor: Upgrade mime from 4.0.4 to 4.0.6 #9546) (ae16aba)
• ci: MongoDB 4, 5 CI jobs fail for LTS branch (ci: MongoDB 4, 5 CI jobs fail for LTS branch  #9536) (0fb0c07)
• fix: Push adapter not loading on some versions of Node 22 (fix: Push adapter not loading on some versions of Node 22 #9525) (5447c22)
• ci: Update auto release (ci: Update auto release #9520) (4ac8aef)
• ci: Udpate auto-release LTS branch (ci: Udpate auto-release LTS branch #9519) (82ab3f9)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release-7.x.x with git revert or git reset.

A valid branch could be release.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀