parse-community / parse-community/parse-server
Add auto-creation of PR for upgrade of MongoDB / Node.js CI env
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Upon fail of ci-self-check a PR has to created manually to update the MongoDB / Node.js versions, before other CI runs pass.
Example of manually created PR: https://github.com/parse-community/parse-server/pull/7184
Feature / Enhancement Description
Add auto-creation of PR when a new MongoDB / Node.js version is released to update the versions in CI environments.
Example Use Case
(none)
Alternatives / Workarounds
Manually creating PR.
3rd Party References
(none)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ci-self-check workflow and the manually created PR #7184 to identify where MongoDB and Node.js versions are defined in CI environments. Trace what currently fails when a new version is released, then determine the repository's existing automation conventions. Done means a new release can trigger an automatically created PR that updates both CI versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb, nodejs
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100