Software or graph infrastructure-related changes.
Pull requests that update Javascript code
Test coverage improvements that were not included in feature prioritization
Dependency updates and their version upgrades.
Adding or improving monitoring or logging of our services for reliability.
Improvement to internal processes
Simplifying or restructuring existing code or documentation.
General improvements to product usability that are unrelated to feature prioritization.
Used to track other issues that are required to complete the milestone.
Work on coming up with a proposal or mockup for a future implementation.
involves researching information on a topic rather than implementing specific feature.
Validating a proposed feature or confirming a proposed solution with the target user
Issue that is not an internal priority, but external PRs to address it are welcome.
Bug fix, will increment patch version when merged (0.0.+1)
Update one or more dependencies version
Change that only affects user documentation
Non-user-facing code improvement, will increment patch version when merged (0.0.+1)
Significant behaviour change that breaks compatibility, will increment major version (+1.0.0)
Non-breaking feature or enhancement, will increment minor version (0.+1.0)
Feature or enhancement that breaks compatibility, will increment minor version (0.+1.0)
Incremental feature improvement, will increment patch version when merged (0.0.+1)
Improve performance of an existing feature, will increment patch version when merged (0.0.+1)
Add or improve existing tests
This change is available in a prerelease.
Minimal planning and/or implementation work required.
Create a release when this PR is merged
This issue/pull request has been released.
Used to describe the roadmap and track milestone issues needed to complete it.
A bug or broken feature with no workaround
A broken feature with a workaround that is unacceptably complex